1 min lesson
Reset one chat and verify the controls
Reset one stale chat. Test the ignore rule and check the privacy settings against current docs.
Step 1 of 2
Take one chat that changed goals or repeated a failed fix. Decide whether the goal changed or only the context grew. If it changed, summarize the settled decisions, open a new chat, state the new finish line and attach current evidence. Test a .cursorignoreA file listing paths Cursor must never index or read, kept separate from .gitignore. Press Enter for the full definition. path through Agent and @, then record the terminal and 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. exception. Use .cursorindexingignore only for a file that should stay out of search but remain readable. Finally, verify Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. enforcement, the selected model and the product path before making a retention claim. Record the exact ignore pattern, Privacy Mode setting, selected model and product surface with the handoff so another reviewer can reproduce each claim. Keep the evidence beside the claim.
Learn more
Full explanation
Context ring, ignore files and Privacy Mode
Summarize only the auth decisions that the rate-limit task still depends on..env.local
fixtures/customer-dump.jsontmp/generated-trace.jsonLearn more
Optional practice
Test yourself on Reset one chat and verify the controls
QWhat should be true when you finish the chat context and privacy controls practice?