Roo Code .roorules
https://roocodeinc.github.io/Roo-Code/features/custom-instructions/
Discontinued: Roo Code (VS Code agent) used .roorules / .roo/rules files as persistent project instructions; the extension shut down on 2026-05-15 and its repo is archived.
Archived · Verified 2026-10-29 · fresh as of 2026-10-29 · 29 cited facts, 0 with a third-party source · 2 recorded changes · Suggest a correction
At a glance
- Type
- Per-mode rules + workspace overrides vendor fix
- Tier
- T2
- Section
- File-backed / editor paradigms
- Created
- 2024-12 (Roo Code forked from Cline in late 2024; .roorules added as distinct pattern post-fork) registry fix
- Latest release
- not applicable — not OSS fix
- License
- Apache-2.0 repo fix
- Pricing
- not applicable — not commercial fix
- Funding
- not applicable — not commercial fix
- Freshness
- 2026-10-29 fix
- Layer
- agent-infra repo fix
- Licensing
- open-source repo fix
Memory taxonomy
- storage
- file
- retrieval
- injection
- persistence
- cross-session
- update
- overwrite
- unit
- document
- governance
- user-controllable
- conflict
- manual
When to use
Optimised for: simplicity / git-versioned / human-readable
Anti-fit: not for non-coding / non-IDE use cases
Pros & cons
Pros
Roo Code's rule file — git-versioned conventions distinct from Cline's despite forking heritage.
Cons
Roo-only; rule format diverges from Cline so cross-tool portability isn't trivial.
Claims & capabilities
VS Code extension (fork of Cline).
Technical surface
- API surface
- not applicable — config file
- Backend storage
- file (.roorules)
- Deployment
- not applicable — not a deployable product
- Embedding model
- not applicable — config file
- Multi-tenancy
- not applicable — local file
- MCP
- not applicable — file-as-memory paradigm (no API surface)
- A2A
- not applicable — file-as-memory paradigm
- OpenTelemetry
- not applicable — file-as-memory paradigm
Alternatives to Roo Code .roorules → live options ranked by shared design, licence, hosting and MCP support
Similar systems
Other file-backed / editor paradigms in the catalog, ranked by inbound references.
- Cline .clinerules T2
Markdown rule files in a workspace .clinerules/ (or .cline/rules/) directory plus global rules in ~/Documents/Cline/Rules; workspace wins on conflict. Per-rule toggles, conditional rules via YAML 'paths' globs, and AGENTS.md / .cursorrules / .windsurfrules are also read.
- OpenClaw memory T3
Memory system of the viral OpenClaw personal agent: plain Markdown files (USER.md, MEMORY.md, daily memory/YYYY-MM-DD.md notes, DREAMS.md) with memory_search/memory_get tools, automatic pre-compaction flush and a 'dreaming' sweep that distils daily notes into long-term memory; pluggable engines (LanceDB, Honcho, wiki). spawned an ecosystem of memory plugins (memory-lancedb-pro, gbrain, MemClaw)
- AGENTS.md T1
Open Markdown 'README for agents' at repo root; nested files in subprojects take precedence (closest wins). Holds build/test commands, conventions and PR rules. Stewarded by the Agentic AI Foundation (Linux Foundation); supported by Codex, Jules, Cursor, Copilot, Gemini CLI, Devin/Windsurf and others.
- Aider CONVENTIONS.md / .aider.conf.yml T2
CONVENTIONS.md (any name, loaded via --read or read: in config); .aider.conf.yml (home / git-root / cwd, last wins); .aiderignore (gitignore-syntax).
- Basic Memory T3
Local-first MCP memory where each memory is a Markdown note with observations and wikilink relations that form a traversable knowledge graph, indexed with SQLite (optional Postgres vectors), plus an optional hosted cloud. widely used MCP memory server with a paid cloud tier
- CLAUDE.md T1
CLAUDE.md files (managed, user, project, local scopes) concatenated into context at session start, with @imports and path-scoped .claude/rules/; complemented by Claude-written auto memory (MEMORY.md index). Project-root file re-injected after /compact.
Sources (28 cited facts, 0 third-party)
Each fact links to the page it came from; the badge says who published it (how to read sources).
- What it is Per-mode rules + workspace overrides vendor
- What it does & what's distinct Discontinued: Roo Code (VS Code agent) used .roorules / .roo/rules files as persistent p… repo
- Claims / benefits VS Code extension (fork of Cline). vendor
- Modalities text vendor
- Created 2024-12 (Roo Code forked from Cline in late 2024; .roorules added as distinct pattern po… registry
- License Apache-2.0 repo
- GitHub RooCodeInc/Roo-Code — ~24.3k stars, archived (last push 2026-05-15) repo
- Founders / pedigree Roo Code (open-source VS Code extension; community-maintained) vendor
- Memory volume / scale no scale claim — markdown files vendor
- Backend storage file (.roorules) vendor
- Consistency strong vendor
- Versioning snapshots vendor
- Tombstoning hard-delete supported vendor
- Schema evolution free-form / no schema vendor
- Namespace primitives hierarchical vendor
- Contradiction handling always overwrite (last-write-wins) vendor
- Forgetting policy user-controlled forget vendor
- Import / export Markdown / plain text (the file itself is the export) vendor
- Validated verticals coding agents only - software engineering teams vendor
- Time to running <10min (drop a file in repo) vendor
- Anti-fit not for non-coding / non-IDE use cases vendor
- Optimised for simplicity / git-versioned / human-readable vendor
- Adjacent infrastructure requires the corresponding IDE / editor vendor
- Pros Roo Code's rule file — git-versioned conventions distinct from Cline's despite forking h… vendor
- Cons Roo-only; rule format diverges from Cline so cross-tool portability isn't trivial. vendor
- Project & sources custom instructions docs vendor
- licensing-bucket open-source repo
- taxonomy-three-layer-rollup agent-infra repo
What changed
Changes to this record's lifecycle, licence, release, pricing and hosting facts, from the catalog's git history. Subscribe (Atom)
Related systems
References (1)
- Cline .clinerules forks — VS Code extension (fork of Cline).