Open-Sourced CLAUDE.md Keeps Claude Code Agents Productive for Hours, Not Looping

If you've run autonomous Claude Code sessions, you've hit the wall: agent starts sharp, drifts into narration by hour 2, loops on the same fix by hour 3, then dies with nothing shipped. One developer who burned through hundreds of sessions found the culprit wasn't a framework or tool — it was a missing CLAUDE.md file in the project root.

What the Operating File Does

The file is 70 lines, MIT licensed, and sits at ./CLAUDE.md. Claude Code reads it at startup and behavior shifts immediately. The core directives:

• Forces action over narration. If the agent catches itself writing "I will now" instead of calling a tool, it stops and fires the tool.
• Requires evidence before claiming done. No "should be fixed" without test output.
• Kills planning language. The only valid outputs are completed actions, questions, or summaries.
• Self-audits on context pressure instead of silently degrading.

Impact on Sessions

With the file in place, sessions went from 3-hour narration loops to full productive lifecycles. The agent ships code, verifies it landed, and keeps going until context pressure hits. Then it saves state and the next session picks up clean.

How to Use

Copy the file from the GitHub repo into your project root. No setup, no dependencies. Claude Code reads it automatically. The repo contains the exact CLAUDE.md — grab it and drop it in.