What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Cursor doesn’t remember your project between completions, and its Rules documentation says so directly: large language models do not retain memory between completions. What looks like “forgetting” is usually a new request that didn’t include the earlier guidance. The fix is to move what you keep repeating into places Cursor reads every time (project rules or AGENTS.md), attach the right code to each task, and rule out indexing or ignore-file problems before you retype your explanation.
Why Cursor seems to forget
Cursor builds each request from the context it is given: your prompt, attached references, applied rules, and whatever it automatically estimates is relevant. Anything you explained in an earlier chat is present only if it is still in that conversation’s context or is pulled in again. So the useful question is not “how do I make it remember?” but “which of these three layers does this information belong in?”
- Durable project instructions: conventions and decisions that stay true across tasks.
- Task context: the specific code and constraints for the change in front of you.
- Discovery: whether Cursor can see your files at all.
Note on sourcing: everything described below as a feature comes from Cursor’s documentation (Rules, Context guide, @ symbols, Folders, Ignore files, Memories, and Troubleshooting pages). Parts labelled as a template or habit are my workflow recommendations, not Cursor-prescribed behavior. Cursor’s UI changes often, and some of its reference pages are older than others, so confirm labels in your installed version.
Step 1: Put durable knowledge in the repository
What belongs in rules
Cursor documents version-controlled project rules under .cursor/rules, global user rules, and AGENTS.md as a plain Markdown alternative. Rules can apply to the whole project or be scoped to certain files. The current Rules page describes the older .cursorrules file as legacy, so use the newer formats for new projects.
Recommended Free Tools
#1 Best Overall
Good candidates are facts you would otherwise retype:
- Architecture conventions and boundaries between modules
- Naming and file-layout patterns
- How to run tests, linting and builds
- Decisions that constrain future changes (for example, “we chose X over Y because…”)
How to keep rules effective
Cursor recommends focused, actionable rules and splitting large concepts into smaller ones. Reserve always-applied guidance for what is truly project-wide; a long architecture narrative applied to every request spends attention on unrelated tasks. A better pattern is a short rule that points to the source document or directory the Agent should inspect. In a monorepo or a repo with distinct subsystems, scope rules to the relevant paths.
Because rules live in the repo, they are reviewed, versioned and shared with teammates, which a chat history never is.
Step 2: Give each task a context packet
Cursor says it automatically pulls in what it judges relevant, but its guidance is to steer it with precise @ references:
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →@Codefor a specific symbol@Filesfor a specific file (you can also drag and drop files in)@Folderswhen a whole directory is genuinely relevant
In Chat, long file references may be chunked and reranked by relevance, so a huge file is not guaranteed to be read end to end.
Be careful with folders
A folder reference may give Cursor a path and overview rather than every file. There is an optional Full Folder Content setting, but when a folder exceeds the available context Cursor manages what fits, and in Max mode full folder content may increase request cost. When you know what matters, attach a targeted set of files instead.
A reusable task template
This is a suggested format, not a Cursor feature:
Goal: [specific change] Constraints: [compatibility, style, behavior] Relevant code: @[file or symbol], @[test or caller] Before editing: inspect the existing pattern and tell me which files define it. Done when: [observable behavior and verification]
The “before editing” line makes Cursor show which files it is relying on, so a missed file is visible before it writes code.
Step 3: Keep decisions retrievable
When a long discussion settles on a convention, move the outcome out of the chat. Cursor’s context guide notes that rules can be generated from an existing conversation with /Generate Cursor Rules. Review the result and trim it; generated rules are a draft. For decisions with broader value, put them in your normal project documentation and have a rule point to it.
Past chats and recent changes
The @ symbols overview lists @Past Chats and @Recent Changes, which can bring in earlier session material or recent edits when that is what the task needs. Use them as aids for the current task, not as the canonical record of architecture decisions.
Memories
Cursor describes Memories as rules generated automatically from Chat conversations and scoped to a project; the Rules page says you can view or delete them under Settings → Rules. An older Rules page states Memories are unavailable with Privacy Mode enabled. Since documentation snapshots differ in age, check that Memories are actually enabled in your installed version, and don’t rely on them capturing everything important.
Step 4: When Cursor misses files, diagnose before re-explaining
Cursor’s troubleshooting page (titled around “Why isn’t Cursor picking up my files?”) suggests this order:
- Check whether
.cursorignoreexcludes the file or folder. - Check
.gitignore; Cursor respects those patterns as well. - Reindex the project using the Reindex command from the command palette.
- Attach the file directly with
@filenameand confirm the preview shows the intended path, which matters when several files share a name.
Ignored files do not enter context through normal references, so reindexing won’t surface something you excluded on purpose. Also, ignore files are not a full security boundary: Cursor notes that terminal commands and MCP tools sit outside these file access controls.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesBest Value
Step 5: Connect knowledge that lives elsewhere
If your canonical decisions are in a knowledge base or project-management tool, Cursor’s context guide describes MCP as the way to connect them. Referencing the live source beats pasting a stale copy into chat. Apply access controls at the tool level, given the MCP caveat above.
Which tool for which problem
| Method | Best for | Persistence and scope | Main limitation |
|---|---|---|---|
Project rule or AGENTS.md |
Stable architecture, conventions, workflows | Stored in the repo; rules can be scoped | Long or poorly scoped guidance adds irrelevant context |
@Code, @Files, @Folders |
Code for the current change | Attached to the task only | Large folders or files may exceed available context |
| Memories / past chats | Recovering conversational decisions | Project-scoped memories; retrieval of prior chats | Availability and capture not guaranteed |
| Ignore checks and reindex | Missing repository content | Restores discoverability when config is the cause | Can’t expose intentionally ignored files |
| MCP / linked docs | Context in team systems | External source stays canonical | Tool access bypasses ignore-file controls |
A maintenance habit that prevents repeat explanations
Whenever you catch yourself explaining the same thing twice, treat it as a signal. Add one or two lines to the relevant rule, or a pointer to the doc that covers it, and commit it. Prune rules that no longer match the code. Cursor’s documentation offers no measured figures on how much this improves results, so judge it by how often you stop retyping the same background.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
