Migrate from the Code Review bot to Cosmos

Move all active GitHub Code Review bot reviews to Cosmos in one coordinated cutover.

Ready to migrate? Complete Cosmos onboarding first if you’re new, then open Code Review bot settings and select Migrate to Cosmos. The button prepares an Advisor draft without changing your settings or enabling reviews.

If you sign up for Cosmos with a new Augment account, you may be eligible for complimentary credits. Credits are not guaranteed, and migrating an existing Code Review bot setup does not automatically grant them.

What Cosmos adds to code review

Benefit	What it brings to your team
A configurable PR-to-merge workflow	Combine specialized Experts for line-by-line review, risk triage, human-guided review, repair, and runtime verification. Add PR authoring when you want the workflow to cover more than review. A human always makes the final merge decision. Explore the code review pipeline.
Model choice	Select a supported model when configuring an Expert or starting a session, and change it as your needs evolve. See available models.
Team-specific reviews	Use repository guidance, tune Expert instructions, or create a custom Expert for your workflow. Code Review Memory can carry forward repository conventions and useful feedback. Configure a custom Expert · Code Review Memory.
Automation that fits your process	Start reviews from GitHub events or manual commands, filter by repository and event details, and choose a run identity where available. Configure triggers.
More context and tools	Extend an Expert with approved MCP servers such as Sentry or Atlassian, alongside Cosmos’s direct GitHub integration. Configure MCP servers.
Visible review activity	Inspect Expert sessions, run history, findings, and artifacts instead of treating review as a black box. Review the code review pipeline · Manage automations.

This guide moves your active GitHub pull-request reviews from the current Code Review bot on GitHub to Cosmos. The current Code Review bot on GitHub will be sunset. Migrate all repositories with active legacy reviews together in one coordinated cutover; keep repositories already configured as disabled off. Prepare two base shared Cosmos triggers per supported GitHub host, with repository allow-lists, and keep them disabled during setup. If a JSONLogic filter exceeds Poseidon’s 4,096-byte limit, split its repository allow-list across additional non-overlapping shared triggers; include all triggers in the same full cutover. At cutover, disable the legacy triggers for the full active inventory, update the allow-lists, and enable the Cosmos triggers.

The existing Augment GitHub App is used by Cosmos too. Keep its installation and repository access in place during the migration.

Before you start

You will need:

• A Cosmos tenant admin to configure the GitHub integration, the Deep Reviewer expert, and automations.
• A GitHub organization admin if the existing Augment GitHub App installation needs access to additional repositories.
• Access to the Code Review bot settings page, where you can use Migrate to Cosmos.

Review the prefilled inventory for tenant-level Code Review bot status, each repository’s exact owner/repository name and saved trigger, author allow/deny lists, connected MCP server IDs, and any custom review guidance you want to carry over.

Keep the current Code Review bot settings unchanged while preparing Cosmos. Configure the shared Cosmos triggers disabled with the complete allow-lists. At the approved full cutover, disable legacy triggers for all active repositories in the inventory, then enable the Cosmos triggers with those same allow-lists. Keep repositories saved as disabled out of the filters.

What the migration button does

If this is your first time using Cosmos, complete Cosmos onboarding before starting the migration so Cosmos Advisor is available. Then select Migrate to Cosmos in Code Review bot settings. It prepares a draft from the saved, non-secret settings on the page; review and send it to start the Cosmos Advisor session. If the complete prompt is too long for a link, the page copies it for you and offers a separate link to open Advisor. The button does not change Code Review bot settings, create the Deep Reviewer expert or automations, configure trigger filters, or enable anything. Check the repository inventory before sending the prompt.

Or start from this prefilled Cosmos Advisor session. This link opens a generic draft; it does not load settings from Code Review. Add the recorded settings and custom review guidance, then send the prompt to start the session.

The button’s prompt includes MCP server IDs, not connected MCP servers. Configure those MCP servers in Cosmos and grant access separately (see MCP configuration). Never paste credentials into Cosmos Advisor.

If the MCP servers you used for Code Review are already connected in Cosmos, you can attach the matching MCP configs to the Deep Reviewer expert. The IDs in the button’s migration prompt can help identify them, but the button does not attach them automatically. Before cutover, confirm the expert has MCP access and the identity Cosmos uses to run reviews is authorized to use those servers.

1. Confirm Cosmos can access the repository

1. Open GitHub integration settings and confirm the organization-level GitHub App connection is active.
2. Confirm the existing app installation has access to the target repositories. Ask your GitHub organization admin to grant access if a repository is missing.
3. Use the organization-level GitHub App integration for review access and posting as Augment. For triggered sessions, choose a dedicated service account under Run sessions as when that option is available; otherwise, use an appropriate trigger owner.

For the setup flow, see Getting Started with Cosmos and Using GitHub as a Tool or Trigger.

2. Set up Deep Reviewer and its triggers

To use Cosmos Advisor, use either option above. Review the draft prompt, add any missing settings or custom review guidance, and send it to start the session. Ask Cosmos Advisor to configure Deep Reviewer only, using the existing Deep Reviewer template as the setup model, and prepare two base shared GitHub triggers per supported host: one pull_request trigger for automatic reviews and one comment trigger with All events selected. Give the comment trigger an advanced JSONLogic filter that ORs PR-conversation comments (issue.pull_request present) with inline diff comments (top-level pull_request present), requires a new human comment containing a review command, and restricts repository.full_name to automatic and manual-command repositories. If a JSONLogic filter exceeds Poseidon’s 4,096-byte limit, split its repository allow-list across additional non-overlapping shared triggers; include all triggers in the same full cutover. Put only automatic repositories in the pull_request allow-list; omit disabled repositories from both. Keep both triggers disabled until the approved full cutover for all active repositories. Never paste credentials.

The PR Author expert is not required to migrate from the Code Review bot; it is a separate expert for creating and maintaining pull requests.

Choose a dedicated service account under Run sessions as when available; this sets the session identity, while the organization-level GitHub App controls posting as Augment. Confirm the app can access each target repository. See Configuring Triggers for permissions.

Configure the shared triggers to match the saved behavior:

• Automatic (pull_request): include only automatic repositories; run for pull requests opened or marked ready for review, excluding drafts.
• PR comments: the combined All events trigger includes both automatic and manual repositories. Its advanced filter matches new human comments containing cosmos review, augment review, or auggie review, and ORs the PR-conversation payload (issue.pull_request) with the inline diff-thread payload (top-level pull_request). This excludes ordinary issue comments and unrelated GitHub events.
• Disabled: omit the repository from both allow-lists.
• Author restrictions: preserve allowlists or denylists where supported. For public repositories, confirm the required membership, collaborator, or contributor access check.

Review both repository allow-lists and event filters before cutover. Keep the shared Cosmos triggers disabled during setup. At the full cutover, disable the legacy triggers for all active repositories in the inventory, then enable the Cosmos triggers with the complete allow-lists. Do not leave a subset of active repositories on the legacy service. The handoff is coordinated but not atomic, so a GitHub event may arrive during the transition.

See Configure a Code Review Pipeline and Automations for more information.

3. Cut over the full inventory

Cut over all repositories with active legacy reviews together. Repositories saved as disabled remain disabled and are omitted from the Cosmos filters. The handoff is coordinated but not atomic: a GitHub event may arrive between disabling the legacy triggers and enabling Cosmos.

1. In Code Review bot settings, disable the legacy triggers for every active repository in the migration inventory.
2. In Cosmos Advisor or the automation settings, set the shared repository allow-lists to the complete active inventory and enable the shared triggers.
3. Confirm that expected reviews start across the migrated inventory and that no duplicate reviews are posted.

Leave saved disabled repositories disabled. Keep the existing Augment GitHub App installation and repository access for Cosmos. After all active repositories have moved and the legacy bot is off tenant-wide, you may add the former manual command as a Cosmos alias.

4. Troubleshoot with Cosmos Advisor

If something does not work as expected during migration, ask the Cosmos Advisor agent to troubleshoot the configuration and help you complete the move.

Do not leave both systems enabled for the same automatic or manual trigger behavior; that can create duplicate reviews.

Learn about Cosmos

• Cosmos Advisor.
• Configure a Code Review Pipeline.
• Automations.
• Event Log.