Codium to Qodo: the full rebrand and product map

The short chronology

CodiumAI began with quality-aware developer tooling, especially code and test generation. The company also created PR-Agent, an open-source project for describing, reviewing, improving, and discussing pull requests. Those two paths established the product thesis: generation should be paired with evidence and review so teams can increase output without treating plausible code as correct code.

On 30 September 2024, CodiumAI announced the Qodo name. The company said the name combined quality and code and reflected a wider code integrity platform. Codiumate, the IDE product, became Qodo Gen. The hosted commercial evolution of PR-Agent became Qodo Merge. The Qodo brand gathered generation, tests, pull request review, and quality practices under one name.

The suite expanded with Qodo Command for configurable CLI agents and Qodo Aware for codebase intelligence. Then the naming consolidated again. Qodo's current site says it no longer uses Qodo Merge, Qodo Gen, or Qodo Command as separate product names. Qodo Merge is now Git, Qodo Gen is now IDE, Qodo Command is now CLI, and Qodo Aware is now Context Engine. Current documentation centers the commercial platform on AI code review, rules, context, governance, and developer review tools.

Why CodiumAI chose the Qodo name

The official rebrand announcement framed Qodo as a combination of quality and code. CodiumAI had moved beyond one test-generation assistant into tools across planning, writing, test coverage, and pull request review. A company name tied closely to one earlier product made the wider code-integrity position harder to communicate. Qodo was meant to give the platform one quality-first identity.

The code-integrity phrase connected several stages. Qodo Gen could generate code and tests in the IDE. Qodo Merge could inspect and improve a pull request. PR-Agent gave the review approach an open-source foundation. Later Command and Aware extended the thesis into configurable agents and deeper repository context. The current review-first platform carries the same concern in a narrower commercial message: every proposed change should be evaluated against code, history, requirements, and standards before production.

Qodo's rebrand article also said Codium would remain the name of foundation models behind the platform at that time and that the platform could use other leading models. Treat that as a dated 2024 statement about the architecture and brand, since current product documentation should govern any deployment or model decision made in 2026.

Every old name mapped to the current platform

The intermediate column matters because many active integrations and articles were written during the Qodo Gen and Qodo Merge era. A document titled Qodo Merge review can be accurate for a 1.x tenant and misleading for a current 2.x purchase. A CLI guide for @qodo/gen can describe an alpha release while a current product page simply says CLI. A PR-Agent Docker reference under codiumai can point at a frozen archive while current images use the pragent namespace.

Use Qodo's version picker for commercial documentation. Qodo 1.x preserves the older Merge tools and configuration. Qodo 2.x is the default current review platform. Use the separate PR-Agent documentation for the community project. Mixing those sources can produce a deployment plan that combines commands, pricing, and features from three different products.

CodiumAI and Codeium were different

The names CodiumAI and Codeium differed by two letters and referred to separate companies. CodiumAI became Qodo. Codeium was an AI coding assistant and editor company on a different path. Searches for "codium ai" often blended the two, especially when both had IDE extensions, code generation, and free developer offerings. The Qodo rename reduced that ambiguity and created a new one with old marketplace and package names.

For internal search and support, keep aliases. A user who asks for Codium tests may mean the old Codiumate extension. A user who asks for Codium PR Agent may run a legacy Qodo-hosted app or a self-hosted community deployment. Ask for the installed extension ID, repository URL, package or image namespace, product version, Git provider, and billing portal before giving migration advice.

Avoid correcting the name without resolving the task. The practical answer should say what the old term became and then provide current steps. "CodiumAI is Qodo; Qodo Gen is now IDE; here is the current local review documentation" is useful. "It was renamed" leaves the reader with the same broken path.

What changed beyond the logo

The first rename was a brand consolidation. The later platform shift changed the product center. Qodo 2.0 introduced specialized review agents with repository and PR-history context. Qodo 2.1 added a centralized Rule System. Qodo 2.2 added portal configuration and history-based relevance in selected deployments. Qodo 2.3 added a cross-organization Findings view in beta. Current pricing sells review credits and governance features rather than a broad individual code-generation subscription.

The IDE also moved toward review. Qodo's changelog records local review for uncommitted changes and a review-first welcome flow, while current documentation describes the IDE plugin as formerly Qodo Gen. Qodo's current name-map page still describes IDE as an AI pair programmer with context-aware assistance, test generation, and documentation. Teams should follow the feature set visible in their current version and entitlement because the transition spans old and new product material.

This is why a current Qodo review should avoid judging the product solely as an autocomplete assistant or test generator. Those capabilities explain the company's origin and remain visible in older material. The commercial product now asks to be judged as a review and governance platform. The relevant evaluation is accepted findings, rules, context, deployment, review flow, and cost per useful review outcome.

What happened to PR-Agent

PR-Agent followed a separate ownership change after helping create Qodo Merge. Qodo donated the project to the open-source community in 2026. The repository moved from Qodo's organization to The-PR-Agent, retained the MIT license, and describes itself as community-maintained. The project says the commercial hosted Qodo Merge product evolved into the Qodo 2.x code review platform.

Current PR-Agent still exposes familiar commands, supports several Git providers and deployment forms, and routes to many models. It also changed operational namespaces. The repository notes that Docker releases 0.34.2 and later publish under pragent/pr-agent, while older images through 0.31 remain in the frozen codiumai/pr-agent archive. Current GitHub Action examples use the-pr-agent/pr-agent. Those changes matter for automated updates and supply-chain policy.

Migration checklist for teams and documentation owners

A rebrand becomes technical debt when names appear in workflow files, secrets, package pins, Docker images, dashboards, SSO applications, allowlists, procurement records, training, and support macros. Inventory before replacing. Some old names need current replacements; others identify a legacy system that must keep running until a planned migration.

Search the repository for codium, codiumai, codiumate, qodo-gen, qodo-merge, qodo-command, qodo-aware, old GitHub organizations, old Docker namespaces, and docs URLs. Review results manually. A migration document should keep historical names; an active Action reference may need replacement; a secret called CODIUM_TOKEN may be accepted by old software and rejected by a renamed key.

How to explain Qodo internally now

Use one sentence for the current product and one for history. Current: Qodo is an AI code review and engineering governance platform with Git, IDE, CLI, context, rules, and administration surfaces. History: it was CodiumAI, and older product names include Codiumate, Qodo Gen, Qodo Merge, Qodo Command, and Qodo Aware. Then state separately that PR-Agent is a community-owned MIT project descended from the same origin.

Qodo
Current commercial AI code review and governance platform, formerly CodiumAI.
Current surface names: Git, IDE, CLI, Context Engine.
Legacy names: Qodo Merge, Qodo Gen, Qodo Command, Qodo Aware, Codiumate.

PR-Agent
Separate community-owned MIT pull request reviewer, originally created at
CodiumAI/Qodo. Repository: github.com/The-PR-Agent/pr-agent. It is not the
Qodo free tier.

Codeium
A separate company and product history. Do not use Qodo documentation.

For search and support, include aliases in metadata rather than in every sentence. The page title can use current Qodo while keywords and a glossary catch CodiumAI and Qodo Merge. User-facing setup should use current labels and versioned links. Historical articles should keep the name that was correct at publication and add a dated note at the top.

For procurement, use the current contract product name and describe the licensed capability rather than an old marketing label. "Qodo code review platform, Pro Team shared credits" is clearer than "Codium AI license." For security review, identify SaaS, single-tenant, on-premises, or air-gapped deployment and the model route. Names do not define the data boundary.

Qodo and Continuum after the rename

The rename does not make Qodo an agent orchestration workbench. Its current commercial center is review, rules, context, and governance. Continuum's existing site describes a multi-agent workbench for supported coding CLIs, with one git worktree per session and attached plan, transcript, diff, PR, terminal, and artifact panes. Those jobs can sit consecutively in one delivery path.

Keep the layers named by responsibility. Continuum operates sessions and worktrees. Qodo reviews and governs code changes. PR-Agent provides self-hosted review commands. Tests, compilers, linters, and scanners provide deterministic evidence. Humans approve intent and risk. Product renames then become easier to absorb because the architecture depends on jobs and contracts rather than logos.

Stable role boundaries also make future vendor changes reversible, testable, and easier to explain.

Questions people ask

Keep reading