Your first connected code review.

1. Sign in with GitHub

Select Get started or Sign in. GitHub authenticates your account through Supabase and returns you to the dashboard. Use the GitHub account that has access to the repository you want to review. Apple sign-in is not currently configured.

Sign-in establishes your identity. Connecting a repository is a separate step. If GitHub access expires, use Reconnect GitHub from Workspace settings.

2. Choose your repositories

Open Setup → Repositories → Choose repositories. AntiCode checks the accessible repositories for your verified GitHub account. Select the repository you want to connect.

Private repository access currently uses GitHub’s repo OAuth scope. Review the permission request and your organization’s policy before authorizing access.

3. Sync pull requests

Select Sync pull requests beside the connected repository. The sync imports up to 200 recently updated pull requests. Open Reviews to see their states, authors, and current review coverage.

A sync is a snapshot, not a continuous background feed. Sync again after a new commit, base update, or branch retargeting.

4. Select a review engine

Run checks uses a limited set of server-side deterministic checks. AI review sends the selected pull-request diff to the managed OpenAI service. Review findings are stored in your dashboard.

Do not submit code you are not authorized to process. Large diffs above 80,000 characters are rejected; split the change into reviewable units. If a run fails, the previous successful findings are preserved.

5. Inspect and triage

Open Details and compare the finding’s file and line reference with the pull request. A source match is evidence of location, not proof of correctness. Validate the described trigger and impact.

Use Open, Accepted by me, or Dismissed by me to record your personal decision. Make and test actual code changes through your normal development workflow. AntiCode does not automatically apply these suggestions.

6. Export or disconnect

Use Export to access the data available to your account. Personal severity and path preferences control your view; they do not remove canonical findings.

Disconnect removes your workspace membership immediately. It is not a promise that every stored record is erased. See the privacy page for the current data-handling notice and legal-contact status.

Optional: request a Human Review

Open Human review in your signed-in workspace and select an eligible saved run. Review the bounded sharing preview, explain the question and consent to sharing it with the review team. Source files and suggested patches are not copied into this package; no new AI review starts when you submit.

Request a scope and quote, agree the proposed terms, and follow messages and status in the portal. Submission makes no charge. Only an assigned human reviewer can publish the attributed assessment after scope acceptance. Email notifications contain a request ID and sign-in link, not the evidence or conversation.

Troubleshooting

If a repository is missing, verify access in GitHub and reconnect if needed. If a review reports a changed revision, sync the repository and run again. If a limit is reached, wait for the indicated window.

A failed review must not be treated as a successful clean scan. Open Automations to check GitHub App availability and configure automatic reviews, comment commands and AI suggestions. The App requires separate installation and operator setup. Native upload ingestion and continuous whole-repository monitoring remain unavailable.

• Sign-in loop: allow the site’s essential session cookies and start again from Sign in.
• No pull requests: confirm the repository and sync before reviewing.
• Old findings: check head, base, and branch identity; resync after changes.
• AI unavailable: retain the previous result and retry later, or use an eligible built-in review.

References

• GitHub OAuth scopes ↗