Repository / project instructions
Documented.cursor/rules can supply version-controlled project instructions.
View source detailAgent intelligence
Official Cursor evidence covers rules, memories, agent tools, model choice, and CLI permissions without establishing a published full system prompt.
Cursor is documented as an AI code editor and agent harness with version-controlled project rules, user-level guidance, repository memories, codebase tools, selectable models, and CLI permission controls. The selected official sources do not establish a complete current base system prompt.
Scope: Cursor editor · Cursor CLI · Selectable provider models · reviewed Aug 11, 2026
Reviewed product surfaces
Each layer links to the detailed evidence map. Its state applies only to the reviewed evidence.
Source-backed answers
Each answer is scoped to the selected evidence. “Not established” means the evidence does not support the claim; it does not assert absence.
.cursor/rules can supply version-controlled project instructions.
View source detailUser-level rules provide preferences across projects.
View source detailApproved memories preserve repository-scoped learnings as rules.
View source detailSearch, read, edit, delete, terminal, and MCP tools are documented.
View source detailAllow and deny controls can constrain shell, read, and write operations.
View source detailThe selected official sources do not publish a complete current Cursor base system prompt.
Review evidence scopeEditorial guidance
These conservative editorial implications come from the linked evidence. They add no vendor claims or generic prompt advice.
.cursor/rules is the documented project scope, while user rules provide preferences across projects.
Supporting evidenceMemories preserve repository-scoped learnings as generated rules rather than establishing the hidden base prompt.
Supporting evidenceGlobal and project allow/deny controls can constrain shell, read, and write operations even when the agent has corresponding tools.
Supporting evidenceUseful next actions
Product scope
Evidence status
Official Cursor documentation covers rules, memory, tools, models, and CLI permissions. The review does not claim a complete current base system prompt.
Detailed instruction layers
The map separates the unestablished base prompt from project and user rules, repository memories, agent tools, models, and permission controls.
The selected official sources do not publish a complete current Cursor base system prompt.
Source detail.cursor/rules can supply version-controlled project instructions.
Source detailApproved memories preserve repository-scoped learnings as rules.
Source detailSearch, read, edit, delete, terminal, and MCP tools are documented.
Source detailAllow and deny controls can constrain shell, read, and write operations.
Source detailSupporting instruction evidence
Official sources document the product but do not support a standalone public system-prompt page.
Evidence-backed capabilities
Each capability links to its supporting instruction section and keeps its stated confidence level.
| Capability | What the source establishes | Confidence | Evidence |
|---|---|---|---|
| Agentic codebase work | Cursor's agent is documented as searching, understanding, and changing codebases. | high | Source detail |
| Project and user rules | Project rules and user rules supply persistent model context at different scopes. | high | Source detail |
| Repository memories | Approved memories preserve repository-scoped learnings as generated rules. | high | Source detail |
| Agent tools | Search, read, edit, delete, terminal, and MCP tools are documented. | high | Source detail |
| CLI permission controls | Global and project configuration can allow or deny shell, read, and write operations. | high | Source detail |
| Selectable models | Cursor supports models from multiple providers and an automatic selection mode. | high | Source detail |
Version evidence
The selected evidence establishes no compatible first-party full-prompt snapshots. Documentation updates are not treated as prompt versions.
Provenance
Every source lists its origin, retrieval date, completeness, publication limits, and rights separately.
Establishes the coding-product and agent context, not a complete runtime prompt.
Open primary sourceDocuments rule inputs rather than the complete instruction assembly.
Open primary sourceTool availability and automatic execution can vary with configuration.
Open primary sourceModel availability can change and does not define one universal Cursor runtime.
Open primary sourceDocuments saved memory behavior, not every context input.
Open primary sourceDocuments CLI permission configuration; editor and deployment controls can differ.
Open primary source