Skip to main content
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

This guide moves your GitHub pull-request reviews from the current Code Review bot on GitHub to Cosmos. The current Code Review bot on GitHub will be sunset. Move repositories one at a time or in selected batches. Prepare matching Cosmos triggers disabled; at cutover, disable each repository’s legacy trigger before enabling its Cosmos triggers. Repositories not yet moved stay on their existing setup. 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 matching Cosmos triggers disabled. At each repository’s cutover, disable its legacy trigger, then enable the corresponding Cosmos triggers; leave repositories not yet migrated unchanged.

​
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 and prepare matching triggers for the selected repositories, or configure them directly in Cosmos. Keep every trigger disabled until its repository is ready to move. 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. For each repository, configure Cosmos to match its saved trigger:
  • Automatic: pull requests opened or marked ready for review, excluding drafts, plus review-command comments.
  • Manual: review-command comments only on new human comments on pull requests; ignore bot comments and ordinary issue comments. Match trimmed, case-insensitive cosmos review, augment review, or auggie review.
  • Disabled: do not add review triggers for that repository.
  • Inline comments: add a pull_request_review_comment trigger only if your workflow needs it.
  • Author restrictions: preserve allowlists or denylists where supported. For public repositories, confirm the required membership, collaborator, or contributor access check.
Review the repository and event filters before cutover. Keep all Cosmos triggers disabled while the legacy Code Review bot handles a repository. Disable the legacy trigger before enabling its matching Cosmos triggers to avoid overlapping reviews. See Configure a Code Review Pipeline and Automations for more information.

​
3. Move repositories to Cosmos

Move repositories one at a time or in selected batches. Repositories not yet moved continue using their existing Code Review bot trigger. The switch is not atomic: an event may arrive between disabling the legacy trigger and enabling Cosmos. For each repository or batch:
  1. In Code Review bot settings, disable the legacy trigger.
  2. Enable only the disabled Cosmos triggers that match the saved behavior, using Cosmos Advisor or the automation settings in Cosmos. The legacy trigger must be off before its matching Cosmos trigger is enabled.
  3. Confirm that the expected review starts and that no duplicate review is 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