Roo Code configuration guide: instruction files, MCP, permissions

Roo Code, Inc. · IDE / editor Discontinued · verified against official docs on 2026-10-12

Roo Code was shut down on May 15, 2026 and its repository is archived. Existing installs used .roo/rules/ (or .roorules), mode-specific .roo/rules-<mode>/, global ~/.roo/rules/, and AGENTS.md (on by default). MCP servers were in mcp_settings.json (global) and .roo/mcp.json (project). To migrate, move your rules into AGENTS.md and .roo/mcp.json into the new agent's MCP file. Cline, Kilo Code and OpenCode all read AGENTS.md.

Heads up: DiscontinuedThe Roo Code extension was shut down on May 15, 2026 and its GitHub repository is archived.

Roo Code at a glance

Global instructions✓ Yes
~/.roo/rules/, ~/.roo/rules-<mode>/
Project instructions✓ Yes
.roo/rules/ (preferred) or .roorules; .roo/rules-<mode>/
Nested / subfolder? Not documented
Not documented
AGENTS.md✓ Yes
Root AGENTS.md (or AGENT.md), on by default
Skills (SKILL.md)✓ Yes
.roo/skills/, .agents/skills/; global ~/.roo/skills/, ~/.agents/skills/
MCP config✓ Yes
Global mcp_settings.json; project .roo/mcp.json
Permissions / allowlist✓ Yes
Auto-approve with allowed / denied command prefix lists
Sandbox? Not documented
Not documented
Hooks? Not documented
Not documented
Claude Pro/Max login? Not documented
Not verified (product discontinued)
ChatGPT Plus/Pro login? Not documented
Not verified (product discontinued)
API key / own plan✓ Yes
Your own provider keys

Exact file paths

PathScopeWhat it does
.roo/rules/*.mdWorkspaceRules (fallback .roorules)
.roo/rules-<mode>/WorkspaceMode-specific rules
~/.roo/rules/UserGlobal rules
.roo/mcp.jsonProjectProject MCP servers
mcp_settings.jsonUserGlobal MCP servers

Using a shared AGENTS.md with Roo Code

Native (product discontinued). See one AGENTS.md for every agent, or generate one with the AGENTS.md generator.

Copy-paste examples

Project MCP file to migrate

File: .roo/mcp.json

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}

Safe permissions preset

Migration checklist

File: terminal

# 1. Merge Roo rules into one AGENTS.md at the repo root
cat .roo/rules/*.md >> AGENTS.md        # review and dedupe afterwards
# 2. Keep mode-specific rules as skills or separate sections
# 3. Move .roo/mcp.json servers into the new agent's MCP file
#    (Cline: cline_mcp_settings.json, Kilo: kilo.jsonc "mcp", OpenCode: opencode.json "mcp")
# 4. Recreate your denied commands as the new agent's deny rules

Roo Code and Cline share history, so Cline is the closest switch; Kilo Code also reads AGENTS.md and .agents/skills.

Gotchas

  • The extension is discontinued; don't rely on it receiving security fixes.
  • Roo's denied commands were prefix matches; check how your new agent matches commands before copying the list.

FAQ

Is Roo Code discontinued?
Yes. The Roo Code extension was shut down on May 15, 2026 and the RooCodeInc/Roo-Code repository is archived.
How do I migrate Roo Code rules?
Combine .roo/rules/*.md (and .roorules) into an AGENTS.md at the repository root, move .roo/mcp.json servers to your new agent's MCP config, and recreate your allowed/denied command lists as permission rules.

Sources

Checked against these official pages on 2026-10-12. Cells marked "Not documented" mean we could not find the behaviour in these docs; it may still exist.