The outcome

Learn the interaction loop using a small task with a clear outcome.

Roo Code is a open-source AI coding agent extension for VS Code. Planning, implementing, debugging, and explaining repository changes with specialized modes and visible approval of file, command, browser, and MCP actions. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Install the official extension and configure one approved model provider without placing credentials in the repository.

  2. 02

    Open a clean branch, select the appropriate mode, and provide the task, constraints, and validation commands.

  3. 03

    Keep auto-approval off while Roo inspects the codebase and proposes a minimal plan.

  4. 04

    Review every tool request, changed file, command, test result, and final diff before committing.

Working standard

What good use looks like.

  • State the outcome before the background.
  • Provide the real source material.
  • Review the result before expanding the task.

Roo can read and edit files, execute terminal commands, browse, call MCP servers, switch modes, and create subtasks. Keep auto-approval disabled or narrowly allowlisted, treat repository and web content as untrusted, isolate consequential work, restrict MCP tools and credentials, review cost limits and provider data handling, inspect every diff and command, and never delegate merges, deployments, migrations, or destructive actions without explicit authorization.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.