PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteIf Claude Code seems to ignore your CLAUDE.md, first check whether the file was loaded: run /context and look under Memory files. If it appears there, the issue is usually not discovery: CLAUDE.md is guidance added to conversational context, not a rule-enforcement mechanism. Make the instruction specific, check for conflicts, or use a hook or technical setting when an action must happen reliably.
Check whether the file loaded before changing it
In the affected Claude Code session, run /context and inspect the Memory files section for the expected path. If the file is absent, Claude cannot use its contents in that session. Check its location and the directory from which Claude Code was launched before rewriting the instructions.
![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.
For more detailed diagnosis, Anthropic documents an InstructionsLoaded hook that can log which CLAUDE.md and rules files load, when they load, and why. This can help distinguish startup-loaded files from path-specific instructions discovered later. See Anthropic’s project memory documentation.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsCheck the launch directory and file scope
Claude Code loads CLAUDE.md and CLAUDE.local.md files in its current working directory and the directories above it. A file in a nested directory below the launch location is discovered when Claude reads files in that subtree; it may not appear as a startup instruction. A session launched from a different directory can therefore have a different set of project instructions. The scope and loading behavior are described in Anthropic’s memory documentation.
#1 Best Overall
- If the expected file is at the project root, launch Claude Code from that project or a directory inside it and check
/context. - If the rule is meant only for a subdirectory, put it in that subtree and ensure Claude reads files there; do not assume it was loaded at session start.
- Check ancestor directories for other instruction files that may also apply.
Check whether AGENTS.md is selected
Claude Code can read AGENTS.md, but default selection is conditional. By default, it reads AGENTS.md only when there is no CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md in the working directory or an ancestor. User-level and managed CLAUDE.md files do not count for that particular selection check. In /config, the Project instructions setting can select CLAUDE.md only, both file types, or the default behavior. Consult the current memory documentation for the selection details.
Direct AGENTS.md support requires Claude Code v2.1.277 or later. Anthropic also notes that some sessions on versions before v2.1.281 could not load it. If a project relies on AGENTS.md, check the installed version with claude --version, review the Project instructions setting in /config, and check whether an applicable CLAUDE.md selects different default behavior.
Validate imports and approval prompts
Imports let a CLAUDE.md include other instruction files using @path/to/import. Relative paths resolve from the file containing the import, not necessarily from the launch directory. Imported content is expanded into context at launch, and recursive imports are limited to four hops. A project-level import resolving outside the working directory can require approval; if approval is declined, those imports remain disabled. Details are in Anthropic’s import guidance.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Verify that the referenced file exists and that the relative path is correct from the importing file.
- For a path with spaces, escape each space with a backslash; quoting the path does not import it.
- An
@pathwritten inside a Markdown code span or fenced code block is treated as an example, not an import. - When a file is unexpectedly missing from context, check whether it is over 4 MiB; Claude Code skips files larger than that.
If the file loaded, make the instruction actionable
Anthropic describes CLAUDE.md content as context, not enforced configuration. That distinction explains why a visible file can still be followed inconsistently: vague wording, stale advice, or conflicts with other applicable instructions can leave room for a different response. The guidance and examples below come from Anthropic’s memory documentation.
| Less actionable | More actionable |
|---|---|
| “Format code properly.” | “Use 2-space indentation.” |
| “Test your changes.” | “Run npm test before committing.” |
Review the files that can apply to the task—including ancestor, project, user, and path-specific guidance—for contradictions and outdated rules. Prefer short instructions with headings and bullets. Anthropic recommends keeping each CLAUDE.md under 200 lines where practical. Splitting a long file into imports can make it easier to organize, but imported content still loads at launch and does not reduce its context cost.
Use enforcement for requirements that cannot be optional
Use CLAUDE.md to explain preferred behavior and project conventions. If something must happen at a defined lifecycle point—such as running a command before every commit—a hook is a better fit than prose guidance. For restrictions that need technical enforcement, use permission or settings controls rather than relying on an instruction file. Anthropic distinguishes these controls from behavioral guidance in its project memory documentation.
Rank #4
Inspect settings and run diagnostics
If the file is visible but Claude Code behaves differently from what you expect, inspect configuration separately from instruction context. /status shows which settings sources are active, while claude doctor reports rejected configuration entries. Managed settings take precedence over ordinary personal and project settings, and command-line options can override ordinary settings for a session. Anthropic documents settings precedence in Settings files and precedence.
For a broader check, run /doctor inside Claude Code to inspect installation, settings, extensions, and context usage. If Claude Code cannot start, run claude doctor from the shell. The available troubleshooting routes are listed in Anthropic’s troubleshooting guide and the CLI reference.
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.
