Cursor Rules
https://docs.cursor.com/context/rules
.cursorrules + project rules. Semantic chunking + Merkle-tree incremental re-indexing over the codebase. Turbopuffer-backed retrieval at IDE scale.
At a glance
- Type
- IDE-embedded code memory
- Tier
- T1
- Section
- File-backed / editor paradigms
- Created
- 2023-03 (Cursor launched March 2023; .cursorrules file supported from initial release)
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- not applicable — not commercial
- Funding
- not applicable — not commercial
Taxonomy
- storage
- file
- retrieval
- injection
- persistence
- cross-session
- update
- overwrite
- unit
- document
- governance
- user-controllable
- conflict
- n/a
When to use
Optimised for: simplicity / git-versioned / human-readable
Anti-fit: not for non-coding / non-IDE use cases
Pros & cons
Pros
Rule-file format integrated directly into the IDE that 35M+ developers use; specific selectors (file globs) make rules precise.
Cons
Cursor-only — no portability to Claude Code or other agents; rules can quietly conflict and produce confusing agent behavior.
Claims & capabilities
Cursor at 27.3% market share (2026, behind GitHub Copilot's 41.8%); .cursorrules file is the core behavior-customization mechanism, enabling project-specific instructions read on every session
Technical surface
- API surface
- not applicable — IDE feature
- Backend storage
- file (.cursor/rules/)
- Deployment
- not applicable — not a deployable product
- Embedding model
- not applicable — rules file
- Multi-tenancy
- Multi-tenant AWS with logical segregation; separate tenants for privacy vs non-privacy modes; no dedicated single-tenant offering
- MCP
- not applicable — file-as-memory paradigm (no API surface)
- A2A
- not applicable — file-as-memory paradigm
- OpenTelemetry
- not applicable — file-as-memory paradigm
Compare Cursor Rules with…
Similar systems
Other file-backed / editor paradigms in the catalog, ranked by inbound references.
- Cline .clinerules T2
.clinerules single file or .clinerules/ directory of numbered .md files (e.g. 01-style.md ). Global at ~/.cline/rules/ . Files version-controlled and AI-editable — Cline can write back. Toggleable per-session via UI.
- AGENTS.md T1
AGENTS.md at repo root (and ~/.codex/AGENTS.md for global); hierarchical concatenation from root to cwd. Persists build/test commands, conventions, architecture overview, security constraints, git workflow.
- 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).
- CLAUDE.md T1
Markdown file injected at session start; reloaded post-compaction. Document-as-memory: human-readable, version-controlled, no extraction or vector store. Anthropic-canonical pattern; equivalent emerges in Cursor / Windsurf.
- Cline Memory Bank T2
memory-bank/ directory of Markdown: projectBrief.md , productContext.md , activeContext.md , systemPatterns.md , techContext.md , progress.md . Loaded in full at start of every task. Compensates for context-window reset between sessions.
- Continue.dev .continue/rules T2
.continue/rules/*.md at workspace root. YAML frontmatter: name , globs (file-pattern trigger), alwaysApply , description . Loaded lexicographically.