Sign in to manage your pull request reviews and keep work moving.
Private access to your review settings.
Your pull requests, in one place.
Reviews, follow-ups, and items that need your attention.
Choose where and when the agent works.
Start checking eligible pull requests.
Choose API to use Claude API billing while OpenAI stays on GPT Pro.
Use the owner and repository name, for example your-team/ra-backend.
Subscriptions read complete files on demand from a separate source workspace, with up to 30 MB of stored evidence.
The service starts this workflow for reviewed commits. Leave blank if your checks already run automatically.
Every listed check must pass. CI runs in GitHub.
Enter * to include all current and future target branches, or list one branch per line.
Enter one exact repository-relative path per line. Excluded paths appear in review summaries. Pull requests changing only ignored files are Skipped without an RFM label or email.
Let subscription reviewers search complete safe repository source and fixers edit isolated copies. GitHub CI and verification still gate RFM.
Exclude cosmetic-only function or class length, naming, and formatting findings. Bugs, security issues, and regressions remain required.
Allow the agent to update the pull request branch with its fixes.
Assign a model to each stage of the review.
Saved secrets are never shown. Leave a field blank to keep its current value.
Use a GitHub App installation to publish reviews under the app’s bot name. Existing comments keep their original author.
Choose the downloaded PEM file only when replacing the saved key. Access tokens refresh automatically and remain in memory.
Receive an email when a pull request is marked ready for merge.
Use your organization’s Microsoft 365 email application to send RFM notifications.
Your Microsoft 365 application must have permission to send email from the sender mailbox.
Keep sent notifications in the sender’s mailbox.
Separate email addresses with commas or semicolons.
These limits apply only when using API keys.
In API mode, the agent pauses work when a spending limit is reached. Subscription mode uses your shared account allowance and never falls back to paid API calls. Model prices and output-token settings apply to API calls only.
Changes take effect after you save.