Your first connected code review.

1. Sign in with CodHub

Choose Sign in or Get started and continue with CodHub. Create and verify your account at codhub.org if needed. Existing AntiCode customers should first link CodHub from their signed-in Profile so their workspace and subscription stay attached to the same AntiCode account. This explicit linking flow verifies the current AntiCode session and CodHub identity; it does not select an account by email text.

Available sign-in methods are shown on the sign-in page. The Cloudflare-owned sign-in path does not merge AntiCode accounts by email or profile. Where an additional method is enabled, you can explicitly connect an unbound CodHub or Cloudburg identity to your current account. An identity already connected to another AntiCode account cannot be moved or merged here. Cloudburg sign-in grants identity access only. Repository access requires separate read-only CodHub authorization, including private repositories you may access. Repository authorization must match your linked CodHub identity. Repository tokens are encrypted on the server and are never returned by dashboard APIs.

2. Authorize repository access

In Setup, connect CodHub repositories and review the read-only consent request. The repository account must match the CodHub identity linked to your AntiCode account. After authorization, bounded discovery can connect accessible repositories up to your plan limit; inspect the results and disconnect unwanted projects.

Eligible saved CodHub grants can renew automatically. Revoked access, legacy connections without a saved refresh grant, or uncertain renewal can require reconnecting in Setup. Disconnecting removes AntiCode workspace access; it does not revoke consent at CodHub or erase all stored history.

3. Sync pull requests

Sync retrieves up to 200 recently updated pull requests per repository. Initial discovery reads a smaller bounded page; the interface reports partial coverage. Repository and pull-request identity remain tied to CodHub, not to a matching numeric ID from another provider.

Sync is a snapshot, not an unattended background feed. Sync again after commits, base updates or branch changes. Unavailable provider metadata is not reported as a measured zero.

4. Run eligible built-in checks

CodHub supports read-only repository discovery and bounded pull-request sync. Built-in checks are available only for SHA-1 repositories when CodHub supplies a complete diff with matching file, addition and deletion counts. Missing counts, incomplete diffs and SHA-256 reviews are rejected without replacing previous findings.

A review must match the pull request head, base and target branch. Source-size, time and access limits still apply. Missing metadata or a changed revision stops the run and preserves prior findings.

CodHub AI reviews, automatic reviews, comment delivery, CI ingestion, coding proposals and repository scans are not enabled in this release. Historical GitHub workflows do not establish those capabilities for CodHub. AntiCode does not execute repository code, approve or merge pull requests.

5. Inspect and triage

Inspect the source location and validate the described trigger and impact. Open, Accepted by me and Dismissed by me are personal decisions, not proof that source code was fixed. Make and test changes through your normal development workflow.

6. Export or disconnect

Export the records available to your account. Personal display preferences do not remove canonical findings. Disconnect removes your membership; see the privacy notice for retention and separate provider-consent controls.

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

A missing repository may indicate missing CodHub access, expired consent, the plan repository limit or incomplete discovery. Reconnect if needed and continue the next discovery page.

A missing source count or incomplete diff means built-in review is unavailable for that request. A synchronized SHA-256 repository also needs separate review qualification. Do not treat any of these outcomes as a completed clean review.

References

• CodHub API reference ↗