Advanced
Pick a model and context size, use @ mentions, read the context ring, and ask side questions without derailing Agent.
Context management
Use @ mentions when you know what's relevant, read the context ring, choose a model and window size, and keep tangents in side chats.
4 techniques →-
Which Model and Context Size Should You Pick in Cursor? Rule of thumb, not a vendor recommendation: on The X Subscription, start with Cursor's own models, since those draw on your plan's weekly pool: Composer 2.5 for interactive coding and Grok 4.7 for the hardest long-running tasks. Level 3: Workflows
- 1Composer 2.5interactive work, weekly pool
- 2Grok 4.7long, hard tasks, weekly pool
- 3Claude, GPT, GeminiPremium and higher, prepaid credit
-
How Do You Use @ Mentions in Cursor? Type @ in the chat input, start typing, and pick from the suggestions. Level 3: WorkflowsYou know the filesuse @
- @auth.ts
- @auth.test.ts
- Direct and exact
You don't knowskip it- Describe the behavior
- Agent searches
- Faster than guessing
-
How Do You Check What's Filling Your Cursor Context? Look at the context ring next to the prompt input, which shows how full the window is. Level 3: WorkflowsContext ring
- System prompt
- Tools
- Rulesloads every time
- Skillsdescriptions load every time
- MCPcatalogs load every time
- Subagents
- Summarized conversationdetails can be lost
- Conversationyou control this per chat
-
How Do You Ask a Quick Question Without Derailing Cursor's Agent? Type /side or /btw in the chat input, optionally followed by your question. Level 3: Workflows
- Main threadthe tangent stays in context for the session
- Side chata question, with /side or /btw
- Forka different approach, copies the messages
Can you manage Cursor's context and models?
Three questions on what fills your context, how to ask side questions, and which model pays from where. Answers show right after each pick. No sign-up.
Context is a budget you can see
Past the basics, the biggest gains come from managing what's in the window. Cursor shows this directly: the context ring breaks usage down by category, so you can see whether rules, MCP servers or the conversation is taking the room. That turns a vague feeling that the agent has got worse into something you can check and fix.
Use the tools built for each problem
@ mentions point at what you already know. Subagents keep long searches out of your main thread. Side chats keep tangents out of it. And model choice sets both the window size and who pays, since Cursor's models draw on your weekly pool and third-party models draw on prepaid credit.
What is the most important advanced Cursor skill?
Managing context. Cursor's own course says working with AI models is all about managing the context you provide, and its context ring shows you what's using the space.
Should I give Cursor my whole codebase as context?
No, and you don't need to. Agent can search for files itself, so @-mention only what you know is relevant, and exclude generated or vendored code with .cursorignore.
How do I keep Cursor accurate in a long session?
Start a new chat when the task changes, use side chats for tangents and subagents for big searches, and run /summarize when you need to compress the conversation.