Detailed Analysis
A Reddit thread in r/ClaudeAI has surfaced a small but revealing practice among Claude Code power users: supplementing the now-standard CLAUDE.md file with additional persistent markdown documents that serve as long-term memory and coordination tools across coding sessions. The original poster describes maintaining two supplementary files after a month of using the Claude Code desktop app on a side project — a TODO.md that tracks planned features and future work, co-edited by both the user and Claude itself, and an AUDIT_LOG.md that functions as a postmortem ledger, documenting mistakes, their root causes, fixes, and preventive guidance. The poster reports that this second file in particular has measurably reduced repeat errors, suggesting that giving the model a written record of past failures changes its behavior in subsequent sessions.
This practice reflects a broader adaptation happening among developers using agentic coding tools: treating the filesystem itself as an extension of the model's working memory. CLAUDE.md was introduced by Anthropic as a way to give Claude Code persistent, repository-level context — coding conventions, architecture notes, and instructions that would otherwise need to be re-explained every session. But as users push these tools into longer, more complex projects, a single context file has proven insufficient. The community response has been to informally extend this pattern into a lightweight, self-organized documentation system, with files like TODO.md and AUDIT_LOG.md acting as specialized memory stores — one forward-looking (planning), one backward-looking (error correction) — that the model can read, write to, and reason over across sessions.
The significance of this trend lies in what it exposes about the current limitations and workarounds of LLM-based coding agents. Claude, like other large language models, has no persistent memory between sessions beyond what is explicitly fed into its context window. Rather than waiting for Anthropic to solve this at the model or product level, users are engineering their own solutions using plain text files and version-controlled documentation — effectively building a poor man's long-term memory and reflection system. The AUDIT_LOG.md practice is particularly notable because it mirrors techniques from software engineering postmortems and, more speculatively, resembles rudimentary forms of self-correction or reinforcement that researchers have explored in agentic AI systems: giving a model a record of its own past mistakes measurably improves future performance, even without any change to the underlying weights.
More broadly, this thread is a small data point in the larger story of how AI coding assistants are being integrated into real engineering workflows, where the tooling ecosystem often develops faster than official documentation or best practices. As Claude Code, GitHub Copilot Workspace, Cursor, and similar tools mature, informal conventions like structured memory files, audit trails, and task logs are likely to get formalized — either through Anthropic's own product updates (such as expanded context management, memory features, or native support for multi-file project state) or through third-party frameworks and templates that codify what communities are already discovering through trial and error. The fact that ordinary users are independently converging on similar patterns — separating planning from retrospection, using markdown as a lightweight interface between human and model — suggests these are genuine emergent needs rather than idiosyncratic preferences, and points toward memory and self-correction as key frontiers in the next generation of coding agents.
Read original article →