Skip to main content
The Qodo Agentic Toolbox brings Qodo’s code understanding, coding standards, and review capabilities into your existing coding agent. It does not replace your coding agent or require you to interact with Qodo directly; it extends your agent with Qodo capabilities that support key stages of your agentic workflow. After you install the Agentic Toolbox, continue working with your coding agent as usual. The Agentic Toolbox enables your agent to automatically apply Qodo capabilities for understanding your codebase, applying team standards, reviewing changes, and resolving findings.
The Agentic Toolbox is a separate product from the deprecated Qodo Command CLI (@qodo/command) and Qodo Gen CLI.When you install the Agentic Toolbox, it makes a best effort to remove an existing Qodo Command installation. In some cases, the old installation may not be detected and removed, for example if it was installed under a different Node.js version or through a symlink. If the old installation remains, remove it manually before using the Agentic Toolbox.

​
Qodo tools powering the Agentic Toolbox

The Agentic Toolbox skills use Qodo tools to access the capabilities they need to complete their workflows. The tools are organized into groups based on the type of work they support:
  • Codebase: Understand and search your repositories and code.
  • Cross-repo: Understand relationships and dependencies across repositories.
  • Pull request: Learn from previous pull requests and code review history.
  • PR review: View and manage findings from Qodo code reviews.
  • Skills: Use skills that guide your agent’s work.
  • Rules: Find coding rules that apply to your task.
See Qodo tools for an overview of the available tools and how to access them. For the full list of tools and commands, see the Qodo tools reference.
The Agentic Toolbox extends Qodo Code Review into your local development workflow. After you open a pull request, Qodo Code Review continues to provide automated review and collaboration directly in your pull request workflow.

​
Supported interfaces

The Agentic Toolbox is available through the following interfaces.

​
Agentic Toolbox skills

The Agentic Toolbox provides skills for different stages of your agentic workflow. Your coding agent accesses these skills through agent skills.

​
How Agentic Toolbox skills stay up to date

Agentic Toolbox skills are included with your Agentic Toolbox installation. During interactive use, the Agentic Toolbox periodically checks for updates and installs a newer version in the background when one is available. The updated version is used the next time you run a qodo command. After the Agentic Toolbox updates, the next qodo command refreshes installed, Qodo-managed skills from the skill set included with the installed version. You can also run qodo update to check for and install an update manually. By default, the Agentic Toolbox also adds newly released recommended skills to coding agent environments where you already installed Qodo skills. It does not add skills to environments where you have not installed any Qodo skills, and it does not overwrite skills that you own or have customized.

​
Configure coding agent instructions

Coding agents can use the Agentic Toolbox more effectively when its instructions are included in their agent instruction file. Add the Qodo Agentic Toolbox instructions below to your agent instruction file, such as AGENTS.md or CLAUDE.md, to help the agent use the Toolbox effectively throughout its workflow.

​
For coding agents

​
Default template

Copy the following into your agent instruction file:

​
Qodo Agentic Toolbox

  • Use the installed Qodo skills whenever they are relevant or can provide useful context; let the skill choose the current Qodo commands and flags.
  • For coding or code-review tasks, load relevant Qodo Review Standards when they can affect the work. Apply the rules that fit this repository and stack, and do not fetch them again in the same session if already loaded.
  • When an answer depends on unfamiliar code, debugging or regression analysis, historical precedent, cross-repository impact, or technical documentation that describes real behavior, do not guess—check using Qodo’s codebase and pull-request knowledge. Cite the repository, file/line, pull request, or commit behind important claims; distinguish verified facts from inference.
  • Before opening a pull request, run Qodo’s local pre-PR review with context describing what changed, why, key decisions, and links to the ticket or design. Evaluate every finding against the code and intent; fix only findings that are sound and in scope.
  • After a pull request exists, use Qodo’s structured PR review findings rather than scraping rendered review comments. Confirm the review is complete and covers the relevant commit, then apply the findings in the context of the code, task intent, and user direction. Explain what you fix and anything you deliberately leave unchanged.
  • Perform one review-and-fix pass by default. Continue with another round when it is useful to validate meaningful fixes or when the user requests it, within an agreed limit. Finish when the applicable findings are addressed or another round would not produce meaningful progress, and report what remains.
  • Use read-only Qodo discovery autonomously when relevant. When the work reveals a durable convention, offer to contribute it as a Qodo Review Standard; non-admin contributions become pending suggestions for admin review. Ask before creating a suggestion, administering standards, or performing forge mutations.
  • On authentication errors, run qodo whoami to diagnose the current identity/session and run qodo login when authentication is missing or invalid. If Qodo remains unavailable, gated, or rate-limited, report that clearly and continue with local evidence when safe; do not retry in a loop.