A developer on r/ClaudeAI spent time puzzling over why Claude's code output had suddenly become garbage, only to discover the culprit was a single-character typo buried in their CLAUDE.md configuration file. The typo was silently consuming tokens before Claude ever got to the actual task.
What happened
User _nambiar noticed a sharp, unexplained decline in code quality across their Claude sessions. After digging in — with Claude's help, ironically — they traced the regression to a malformed entry in CLAUDE.md, the persistent instruction file that Claude reads at the start of every session. A single-character typo was effectively front-loading the context window with noise, leaving Claude starved of tokens for the actual work.
Why it matters
CLAUDE.md sits at the top of Claude's context window and gets parsed every session. That makes it a high-leverage file — useful when clean, catastrophic when corrupted. Because it operates silently in the background, a bad instruction or malformed line can degrade output across an entire project without any obvious error signal. No warning. No failure mode. Just steadily worse code.
What to watch
This is a good reminder that persistent instruction files are a sharp tool. If Claude's output quality suddenly drops without any model update or prompt change on your end, your CLAUDE.md is worth auditing first. Keep it lean, validate it periodically, and treat it like code — because as far as Claude is concerned, it is.