How Claude Project Instructions Are Injected — And Why Changing Them Mid-Conversation Breaks History
A Reddit user (OHOLshoukanjuu) dug into how Claude's Project Instructions actually work by asking Claude to print its full system prompt verbatim in both a project and non-project conversation, then diffing the two dumps. Here's what they found.
Key Finding: Single Injection at Start
Project Instructions (and User Preferences) are not re-injected every turn. They get loaded into the system prompt at conversation start and stay in context from there. This means Claude only sees them once, at the beginning.
The Mid-Conversation Change Bug
If you change the project instructions mid-conversation, Claude does not know you changed them. It reads the updated version as if that was the original instruction from the very first message. This leads to two weird behaviors:
- Immediate obedience: If your instructions say "start every response with HELP I'M A BUG" and you get one response following that, then you change to "start every response with HELLO WORLD," the next response says HELLO WORLD.
- False memory: If you ask Claude what the project instructions were for the first turn, it says HELLO WORLD. It will actually conclude it made an error on the first response by not following the instructions it now sees.
No Explicit Label
Project instructions aren't labeled as "project instructions" anywhere in the prompt. Claude follows them, but if you ask "what are the project instructions?" it may tell you there aren't any — because nothing in its context is tagged that way.
How It Was Discovered
The user (on iOS, Max subscriber since 2023, self-described non-developer) asked Claude to print its full system prompt verbatim in both a project conversation and a non-project conversation. By diffing the two dumps and watching Claude's thought process while testing changes, they confirmed the single-injection behavior.
This means: if you rely on project instructions evolving over the course of a long conversation, Claude will rewrite its past understanding to match the latest version of the instructions. The original context is lost.
📖 Read the full source: r/ClaudeAI
👀 See Also
Claude Code Token Waste Fix: Disable Attribution Header for Better Cache Hits
Setting CLAUDE_CODE_ATTRIBUTION_HEADER=false in your shell configuration can improve Claude Code's cross-session prompt cache hit rate from 48% to 99.98%, reducing system prompt processing costs by 7x per session.
Using project narratives to manage memory in large OpenClaw projects
A developer shares a process where after each major milestone, they spawn a separate OpenClaw worker to analyze the codebase and write a 'project narrative' document, which helps identify broken pipelines, redundancies, and missing pieces that the main worker might overlook.
KV Cache Quantization Issues in Local Coding Agents at High Context Lengths
A Reddit analysis identifies aggressive KV cache quantization as the cause of infinite correction loops and malformed JSON outputs in local coding agents like Qwen3-Coder and GLM 4.7 at 30k+ context lengths, recommending mixed precision or reduced context as workarounds.
Claude Cowork file access issue with Google Drive streaming mode and the fix
When using Claude Cowork with Google Drive for Desktop in streaming mode, files may fail to open because Cowork needs real files on disk, not placeholders. The fix involves making specific folders available offline and using standard file formats.