Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →To get Claude Code to remember a project, put stable repository guidance in a project CLAUDE.md, keep personal preferences in user memory, and save a handoff when work crosses context windows. If you meant “continue the conversation,” resume the session separately: session recovery is not the same as loading durable project instructions.
Why Claude Code forgets project instructions
“Forgetting” can describe three different problems: Claude Code may not have been given durable project guidance; guidance may be saved at the wrong scope; or a new or refreshed context may lack the details of the task in progress. Each calls for a different fix. No memory file or resume command guarantees that Claude Code will retain every detail.
![Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results](https://m.media-amazon.com/images/I/415+fSJacsL._SL160_.jpg)
As an Amazon Associate I earn from qualifying purchases.
1. Put shared project guidance in a project CLAUDE.md
Anthropic describes ./CLAUDE.md as project memory for instructions relevant to a repository, including architecture, coding standards, and common workflows. Applicable memory files are loaded when Claude Code starts. If the project has no such file, the /init command can help bootstrap one. See Anthropic’s Claude Code memory documentation.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Write down stable information that changes how Claude Code should work in this repository: for example, where key components live, conventions to follow, and the usual build or test workflow. Keep it specific, organize it under descriptive headings, and review it as the project changes. Treat the file as concise working guidance, not an exhaustive copy of the repository; the value is in making important directions easy to find and maintain.
#1 Best Overall
2. Match the memory scope to the instruction
Project memory and user memory serve different audiences. Put repository facts and team conventions in the project’s CLAUDE.md. Put personal preferences that should follow you between projects in ~/.claude/CLAUDE.md. Mixing the two can make guidance unavailable where it is needed or apply a personal preference more broadly than intended.
If instructions make the main file unwieldy, Anthropic documents importing other files with an @path/to/file reference. The localized memory page describes recursive imports up to five levels; because that detail comes from localized documentation, check the current documentation for behavior before relying on a particular import structure. The same page describes CLAUDE.local.md as deprecated in favor of imports for personal, project-specific instructions.
Use /memory to inspect the memory files Claude Code has loaded. This is a useful first check when an instruction seems to be missing: confirm the relevant file is loaded, then confirm the instruction is in the appropriate scope.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Resume the conversation or hand off task state
If you want to pick up an earlier conversation, use a session-recovery command. Anthropic’s CLI reference documents claude --continue (or -c) for the most recent conversation in the current directory, and claude --resume <session-id> (or -r) to resume a session by ID. These commands recover a conversation; they do not replace durable project instructions in CLAUDE.md. See the Claude Code CLI reference.
For work that spans context windows, save task state before the transition rather than relying on the previous context alone. Anthropic’s prompting guidance recommends saving progress and state to memory before a context window refreshes. A practical handoff can record:
- The task goal and what is already complete
- Decisions made and unresolved questions
- Files changed or examined
- The next action to take
That checklist is a practical format, not a prescribed Anthropic template. The guidance also notes: “Starting fresh versus compacting: When a context window is cleared, consider starting with a brand new context window rather than using compaction.” Whichever route you take, a concise written handoff helps a fresh context recover the task’s important state.
Quick Recap
Rank #4
Which fix should you use?
| Mechanism | Scope | Best for |
|---|---|---|
Project CLAUDE.md |
One repository | Stable project facts and shared team conventions |
User ~/.claude/CLAUDE.md |
Across projects | Personal preferences that should apply broadly |
| Continue or resume command | A specific conversation | Returning to an earlier session |
| Written task handoff | A task crossing context windows | Carrying forward progress, decisions, and next steps |
A quick diagnosis
- Claude Code repeatedly misses a repository convention: add clear, stable guidance to the project’s
CLAUDE.md. - A preference should apply in every project: put it in user memory rather than duplicating it in each repository.
- You started a different conversation: use
--continueor--resumeif you need the earlier conversation, and keep durable project rules in project memory. - A long task is moving to a fresh or refreshed context: write a concise state handoff before switching.
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.
