Qodo Merge is now Qodo Review, and the Qodo Command CLI gives way to the Agentic Toolbox. PR-Agent now runs as a community project outside Qodo. Run local review in the Toolbox, since Qodo set October 30, 2026 as the IDE plugin's retirement date, and replace any v1 commands your scripts still call. Each step below maps an older piece to its replacement.
When you need this
- Your repositories still run Qodo Merge commands or a .pr_agent.toml written in 2024 or 2025.
- Developers use the Qodo IDE plugin or the Qodo Command CLI.
- You self-host PR-Agent and want to know who maintains it now.
Evaluation criteria
Know the current names
Which product are you buying today?
Look forCheck which product your team uses. Qodo's documentation names Qodo Review (v2) as current and Qodo Merge, PR-Agent, Qodo Gen, and Codiumate as historical names.
Replace removed v1 commands
Which of your commands stop working?
Look forQodo deprecated selected v1 commands on September 1, 2026 and scheduled their removal for October 1, 2026. Map improve_code, improve_multi, improve_component, and custom_prompt to agentic_review. Map implement to fix and describe_legacy to agentic_describe. The commands test, update_changelog, add_docs, and create_ticket have no direct replacement.
Run the migration wizard
Is your installation on the current flow?
Look forExisting installations keep working without migration. Run the installation wizard for GitHub, GitLab, Bitbucket, or Azure DevOps to turn on Review Standards, findings, and the other newer features.
Move local review to the Agentic Toolbox
What replaces the IDE plugin and Qodo Command?
Look forThe Agentic Toolbox is a new install, separate from the deprecated Qodo Command and Qodo Gen CLIs. Install it as a CLI, an MCP server, or a plugin for Claude Code, Codex, or Kiro.
Decide on self-hosted PR-Agent
Do you keep running PR-Agent yourself?
Look forIf you keep PR-Agent, pin a version and name an owner. Its README calls it a community-maintained legacy project of Qodo, separate from Qodo's review product. Releases from 0.34.2 use a new Docker namespace. Victor Lyuboslavsky and LightSpeed use their own model keys. OpenVanilla removed its workflow after reviews stopped in April 2025.
Questions to ask vendors
- Which repositories still call v1 commands from scripts or comments?
- Who uses the IDE plugin or Qodo Command, and when do they move?
- Have we run the migration wizard on each Git provider?
- If we self-host PR-Agent, which image and version do we pin, and who patches it?
Red flags
- Automation that posts removed v1 commands and reads their output as a review.
- Developers still relying on the IDE plugin after its October 30, 2026 retirement date.
- A self-hosted PR-Agent pinned to the frozen codiumai Docker namespace.
- Buying Qodo on the strength of PR-Agent accounts without checking the hosted product's current features.
Products in this piece
Sources
- Official documentation
- 5
- Public source
- 4
- Qodo documentation index (current product and historical names)
- Qodo docs: Sunsetting legacy v1 commands
- Qodo docs: Migration guide
- Qodo docs: Integrations (IDE plugin retirement notice)
- Qodo docs: Agentic Toolbox overview
- The-PR-Agent/pr-agent README: a community-maintained legacy project of Qodo (Oct 2026)
- Victor Lyuboslavsky, fleet-edr issue #1141: Run PR-Agent from CI instead of the metered Qodo review (Sep 21, 2026)
- LightSpeed .github issue #3535: Validate the qodo-pr-agent pilot credential boundary and activation (Sep 24, 2026)
- OpenVanilla pull request #230: Remove Qodo's PR agent CI workflow config (Dec 10, 2025)