> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qodo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrating to Qodo v2 FAQ

> Frequently asked questions about migrating from Qodo v1 to Qodo v2, including feature changes, deprecations, and the new Review Standards.

Qodo v2 introduces a unified platform architecture that expands and restructures capabilities previously available in Qodo v1. As the platform evolves across v2.x releases, features may be enhanced, consolidated, or redesigned to support a more scalable and integrated experience.

This guide focuses on feature mappings, deprecations, and required migration guidance for existing functionality. For new capabilities introduced in Qodo 2.x that did not exist in Qodo v1, refer to the [What's New ](/qodo-documentation/whats-new).

### General

<AccordionGroup>
  <Accordion title="Where is Qodo v2 currently available?">
    Supported SCM: GitHub.

    Supported Plans: All plans.

    Supported deployment types: Single-tenant, Multi-tenant and On Premises.
  </Accordion>

  <Accordion title="What’s changed in Qodo v2?">
    Qodo v2 introduces a unified platform architecture. The table below maps current platform capabilities to their equivalents in Qodo v1.

    Items are ordered by the most recent update.

    | Qodo v2 Feature           | Qodo v1 Equivalent                 | Version | Status | Change Summary                                                                                                                        | Supported SCM | Required Action |
    | ------------------------- | ---------------------------------- | ------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------- | ------------- | --------------- |
    | Qodo Review Standards     | Best Practices / Custom Compliance | v2.1    | Beta   | The separate review flows have been unified under PR code review, with best practices and compliance handled by the Review Standards. | GitHub        | Onboard         |
    | Agentic Review Experience | PR-Merge                           | v2.0    | GA     | Replaced with: `/agentic_review`, `/agent_describe`, `/invoke_reviews`                                                                | GitHub        | N/A             |
  </Accordion>

  <Accordion title="What onboarding is required for Qodo v2, and what does it involve?">
    Yes. Migrating to Qodo v2 requires updating your repository configuration to enable the new review commands. Onboarding is designed to be incremental and safe. You can test the new review experience alongside your existing configuration before rolling it out across your organization.

    The onboarding process includes:

    * Updating repository configuration to enable the new review commands
    * Optionally testing the new experience manually in pull requests
    * Enabling the new configuration on a pilot repository
    * Rolling out configuration at the organization level
    * Removing previous review commands to prevent duplicate feedback

    For detailed, step-by-step instructions, see [Migrating to Qodo v2](/code-review/migrating-to-qodo-v2).
  </Accordion>

  <Accordion title="Why should I migrate my existing installation to the new wizard?">
    Migrating gives you full access to available Qodo features and better performance and reliability. Without migrating, your existing installation will continue to work but you may not have access to all available features, and your installation will not appear on the [Repositories page](/governance/repositories).

    For step-by-step instructions, see the [migration guide](/install-and-configure/install/migration-guide).
  </Accordion>

  <Accordion title="What Qodo v1 features and functionality have been deprecated?">
    | Qodo v1 Feature       | Deprecated in Version | Change Summary                                        |
    | --------------------- | --------------------- | ----------------------------------------------------- |
    | `/improve` command    | v2.1                  | Unified under PR review through the Review Standards. |
    | `/compliance` command | v2.1                  | Unified under PR review through the Review Standards. |
  </Accordion>
</AccordionGroup>

### Code review experience Q\&A

<AccordionGroup>
  <Accordion title="Do I need to change my Git workflow?">
    No. Qodo remains fully embedded in your pull request workflow. The review experience is enhanced, but your development process does not need to change.
  </Accordion>

  <Accordion title="What has improved in the PR review experience in Qodo v2?">
    Review feedback is now unified and structured:

    * Issues are grouped by priority (e.g., Action Required, Remediation Recommended, Other).
    * Findings include clear explanations and direct references to code.
    * Reviews include agent-assisted fix prompts.
    * Compliance and code suggestions are no longer separate outputs.
  </Accordion>

  <Accordion title="What is the primary change between Qodo v1 and Qodo v2?">
    In Qodo v2, review is coordinated by a multi-agent system that:

    * Uses specialized review agents to evaluate pull requests from multiple perspectives.
    * Evaluates changes using repository context, pull request history, and organizational standards.
    * Consolidates findings into a single prioritized review.
    * Applies organizational standards through the Review Standards.
  </Accordion>

  <Accordion title="How is feedback structured differently in Qodo v2?">
    | Qodo v1                                                  | Qodo v2                                          |
    | -------------------------------------------------------- | ------------------------------------------------ |
    | Compliance presented as checklist-style outputs.         | Compliance integrated into prioritized findings. |
    | Code suggestions appeared as separate advisory comments. | Suggestions integrated into contextual findings. |
    | Findings not prioritized.                                | Issues ranked by impact and severity.            |
    | Limited explanation of issues                            | Clear reasoning and resolution guidance provided |
  </Accordion>

  <Accordion title="Will reviews look different in my pull requests?">
    Yes. In Qodo v2 you will notice:

    * No separate Compliance or Code Suggestions sections.
    * A more coordinated and prioritized review flow.
    * Clearer explanations tied directly to code.
    * Emoji acknowledgment (👀) when invoking agent commands.
  </Accordion>

  <Accordion title="Where can I find a full list of Qodo configuration options and commands?">
    Qodo provides a set of configuration options that allow teams to control how reviews behave and how feedback appears in pull requests. In addition, pull request commands can be used directly in PR comments to run reviews, generate summaries, ask questions about code changes, and perform other actions.

    For the complete list of supported configuration settings and pull request commands, see the [Configuration and Command Reference](/code-review/get-started/configuration-overview/configuration-and-command-reference).
  </Accordion>
</AccordionGroup>

### Review Standards Q\&A

<AccordionGroup>
  <Accordion title="What are Review Standards?">
    Review Standards are a core part of the Qodo v2 review experience. They:

    * Capture your organization’s standards.
    * Apply them consistently during pull request reviews.
    * Surface findings as structured rule violations.

    When rules are not supported in a given environment, Qodo uses Qodo v1 review logic.
  </Accordion>

  <Accordion title="Does Qodo automatically generate rules from pull request history?">
    Qodo analyzes your organization's pull request history automatically using Rule Miner. When enabled, Rule Miner scans PR discussions across your repositories on a recurring schedule, identifies recurring review patterns, and generates suggested rules without any manual trigger.

    See [Generate rules from pull request history with Rule Miner](/governance/rule-enforcement/rule-miner) for details on how to enable and configure it.

    The `/scan_repo_discussions` command, which previously allowed manual rule discovery, has been deprecated.
  </Accordion>

  <Accordion title="What happens when I add new rules to a supported file in my repository?">
    After onboarding, Qodo monitors the supported rule files across your repositories. When a supported file is updated or a new supported file is added and merged to your repository, new rules are automatically added to your Review Standards as active rules.

    **Single-tenant customers:** If you installed Qodo before the new setup wizard, additional setup may be required.

    For full details, see [Automatic rule updates from files](/governance/rule-enforcement/generate-and-manage-rules).
  </Accordion>

  <Accordion title="What do existing customers need to do when moving to Review Standards?">
     In Qodo v2, Best Practices and Custom Compliance files are replaced by Review Standards, which provide a more powerful and flexible way to define, manage, and enforce review policies across your organization.\
    For existing customers, Qodo automatically ingests existing Best Practices and Custom Compliance files into the [Review Standards](/governance/rule-enforcement) framework, where these rules can then be reviewed and managed.
  </Accordion>
</AccordionGroup>