1 min lesson
The context layer is the actual product
Say what this means in practice: "Retrieval quality is the moat and it is also where the product breaks most visibly."
Step 1 of 3
The context layer is the actual productwhere output quality is won or lost
A model is a commodity you can rent from three vendors. What makes Cursor's output good is which code it puts in front of that model. Retrieval quality is the moat and it is also where the product breaks most visibly.
Learn more
Advanced table
Reference table
- Surface
- Codebase indexing
- What it does
- Embeds the repo so Chat and Agent can retrieve relevant code
- Where it breaks
- Stale or partial index on a large monorepo silently degrades every answer
- Surface
- @-symbols
- What it does
- Pull specific files, folders, docs or symbols into context on demand
- Where it breaks
- Users don't know what to attach, so they get generic answers and blame the model
- Surface
- Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition.
- What it does
- Persistent instructions: stack, conventions, do/don't, file patterns
- Where it breaks
- No rules means inconsistent house style across a team; bloated rules dilute every prompt
- Surface
- MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition.
- What it does
- Connects Cursor to external tools and data via an open protocol
- Where it breaks
- Each integration is a new failure surface - auth, latency and trust all in play
| Surface | What it does | Where it breaks |
|---|---|---|
| Codebase indexing | Embeds the repo so Chat and Agent can retrieve relevant code | Stale or partial index on a large monorepo silently degrades every answer |
| @-symbols | Pull specific files, folders, docs or symbols into context on demand | Users don't know what to attach, so they get generic answers and blame the model |
| Project RulesVersion-controlled instructions in the repo that every Cursor agent interaction inherits, so standards are encoded once. Press Enter for the full definition. | Persistent instructions: stack, conventions, do/don't, file patterns | No rules means inconsistent house style across a team; bloated rules dilute every prompt |
| MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. | Connects Cursor to external tools and data via an open protocol | Each integration is a new failure surface - auth, latency and trust all in play |
When the product feels dumb, the cause is almost always context, not the model.
Cursor's VS Code fork heritage is a real product constraint worth naming out loud. It buys instant familiarity and a working extension ecosystem on day one. It also means Cursor inherits an editor architecture it did not design from scratch and it must track upstream VS Code while building a model-assisted editing experience on top.
- Free / Hobby
- Limited Tab and slower/premium request quotas - enough to build the habit, not to live in it
- Pro (individual)
- Full Tab, generous fast-request and Agent access; the daily-driver tier for one developer
- Teams / Enterprise
- Org admin, centralized billing, privacy mode enforcement, SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition./SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave. Press Enter for the full definition. and usage controls
- The gate that matters
- Individual tiers gate usage; enterprise tiers gate control - admin, security and deployment
Pricing is a product surface: it decides who can adopt and who can govern.
Learn more
Optional practice