1 min lesson
The context layer is the actual product
Show why this lesson detail matters. "Retrieval quality is the defensible edge, 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 several vendors. What makes Cursor's output good is which code it puts in front of that model. Retrieval quality is the defensible edge, and it is also where the product breaks most visibly.
Learn more
Advanced table
When the product feels dumb, check context before you check the model
- 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, check context before you check 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.
Plans and what they gate
- Free
- Limited usage. Enough to build the habit, not to live in it
- Plus ($8)
- Grok and ComposerCursor's own fast coding model, tuned for the editor and priced well below frontier models; the recommended day-to-day model for executing a plan. Press Enter for the full definition. models only, with no Auto, cloud agents, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. or your own API keys
- Premium ($30) and up
- Premium gives 4x the usage of Plus; Super ($100) and Ultra ($200) give 15x and 50x. Cloud agents and automations, BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. and third-party models at API list price start at Premium
- Teams
- Premium, Super or Ultra seats with admin, centralized billing, SAMLSecurity Assertion Markup Language. The XML-era enterprise standard that powers single sign-on: your identity provider vouches for you to each app. Older than OIDC but still what many enterprise tools speak. Press Enter for the full definition./OIDCOpenID Connect. The modern single sign-on standard, built as an identity layer on top of OAuth 2.0. Where SAML is XML and enterprise-legacy, OIDC is JSON and what newer tools implement first. Press Enter for the full definition. SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. and team-wide privacy settings
- Enterprise
- Adds 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. seat management, audit logs and granular spend controls
- Legacy plans
- Hobby, Start, Pro and Pro+ are legacy plans that keep working for existing customers
- The gate that matters
- Individual tiers gate usage; enterprise tiers gate control: admin, security and spend
Pricing is a product surface: it decides who can adopt and who can govern. Plan names and prices follow cursor.com/pricing; check it before you quote a number.
Learn more
Optional practice