AI coding tools
Roo Code Operating Card
Use Roo Code modes, checkpoints, and granular approvals without treating auto-approval as a substitute for scope and review.
- Format
- Reference
- Level
- Beginner
- Audience
- Practitioner, Developer
- Owner
- Project42 Editorial
- Review cadence
- Every 30 days
- Prerequisites
- A supported Roo Code editor installation; An approved model-provider path; A version-controlled workspace
Use modes to limit the current job
Roo Code provides task modes, tools, subtasks, MCP integration, checkpoints, and configurable approvals in an editor. Choose a planning or question mode when mutation is unnecessary and a coding mode only for a bounded implementation.
Auto-approval bypasses confirmation prompts and can increase the effect of a mistake. Enable it only for individually reviewed actions and trusted targets.
Keep checkpoints and Git roles distinct
Define the workspace, protected paths, allowed commands, MCP servers, and required checks. Review mode changes and subtask creation when they would expand authority.
Use checkpoints for local comparison and recovery, while relying on Git branches, commits, tests, and human review for authoritative delivery.
Task: [one bounded result]
Scope: [workspace, paths, and mode]
Permissions: [read, write, command, browser, MCP, subtasks]
Auto-approval: [specific reviewed actions only]
Protected targets: [secrets, external systems, destructive operations]
Verification: [checkpoint diff, Git diff, and tests]
Recovery: [pause approvals, restore checkpoint or Git state]Expected evidence and verification
Expected evidence includes the chosen mode, approval configuration, checkpoint comparisons, Git diff, command history, and test results. Confirm each enabled MCP tool has the intended data and side-effect boundary.
If an auto-approved action crosses scope, disable auto-approval, stop the task, preserve the record, restore the affected state, and narrow the action list before continuing.