> ## 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.

# Sunsetting legacy v1 commands

> Learn which legacy v1 commands are being deprecated and removed, the timeline for each batch, and what v2 alternatives are available.

Qodo is sunsetting selected legacy v1 commands as we consolidate functionality around the current Qodo experience.
The sunset happens in two batches:

* September 1, 2026: Selected v1 commands are deprecated. When you use a deprecated command, Qodo provides guidance and, where available, links to the recommended alternative.
* October 1, 2026: The remaining affected v1 commands are permanently removed.

If you use any of the affected commands listed below, update your workflows before the commands are removed.

## Timeline

| **Date**          | **What happens**                                                                                                                                                    |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| September 1, 2026 | Batch 1: Selected v1 commands are deprecated. When you use a deprecated command, Qodo provides guidance and, where available, links to the recommended alternative. |
| October 1, 2026   | Batch 2: The affected v1 commands are permanently removed.                                                                                                          |

## Batch 1: Commands being deprecated

The following v1 commands are deprecated starting September 1, 2026:

| **v1 command**          | **v2 alternative**            |
| ----------------------- | ----------------------------- |
| `test`                  | No direct replacement         |
| `improve_multi`         | `agentic_review`              |
| `update_changelog`      | No direct replacement         |
| `custom_prompt`         | `agentic_review`              |
| `improve_code`          | `agentic_review`              |
| `config`                | No direct replacement         |
| `add_docs`              | No direct replacement         |
| `help`                  | Qodo documentation            |
| `create_ticket`         | No direct replacement         |
| `inline_comment_router` | Handled by the agentic engine |
| `improve_component`     | `agentic_review`              |
| `implement`             | `fix`                         |

## Batch 2: Commands moving to v2 alternatives

The following v1 commands are being migrated to their v2 alternatives:

| v1 command                | v2 alternative                   |
| ------------------------- | -------------------------------- |
| `describe_legacy`         | `agentic_describe` or `describe` |
| `agentic_describe_legacy` | `agentic_describe`               |
| `generate_labels`         | `agentic_describe`               |
| `checks`                  | No direct replacement            |

## What you need to do

If you use an affected v1 command:

1. Identify where the command is used, including scripts, automation, and regular workflows.
2. Check which batch applies to the command.
3. Review the recommended v2 alternative, if one is available.
4. Update your workflows before the command is permanently removed.
5. Test your updated workflows to make sure they continue to work as expected.

If a command does not have a direct replacement, its functionality will no longer be available after removal.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why are legacy v1 commands being sunset?">
    Qodo is consolidating functionality around the current Qodo experience. This reduces duplication, simplifies the command experience, and allows Qodo to focus improvements on current product capabilities.
  </Accordion>

  <Accordion title="Is Qodo v1 being removed?">
    No. This announcement applies only to the v1 commands listed in the two batches on this page.
  </Accordion>

  <Accordion title="What should I use instead?">
    See the tables above for the recommended v2 alternative for each affected command.

    Some commands do not have a direct replacement because their functionality is being removed or is now handled elsewhere in Qodo.
  </Accordion>

  <Accordion title="What happens when I use a deprecated command?">
    Starting September 1, 2026, Qodo displays a message explaining the change and, where available, provides links to the relevant documentation and recommended alternatives.
  </Accordion>

  <Accordion title="When will the commands be permanently removed?">
    The affected commands are scheduled for permanent removal on October 1, 2026.
  </Accordion>

  <Accordion title="Do I need to update my workflows?">
    Yes. If you use an affected command in scripts, automation, or regular workflows, update them to use the recommended alternative before the command is permanently removed.
  </Accordion>

  <Accordion title="Where can I get help?">
    If you have questions about the sunset or need help identifying the appropriate alternative, contact your Qodo account manager.
  </Accordion>
</AccordionGroup>