What do you put in AGENTS.md when a coding task gets messy?

Reddit r/openclaw Tools

Summary

Discusses how developers using OpenClaw can keep context for AI coding agents by using a handoff document (AGENTS.md) to track goals, files, failures, and decisions in messy coding sessions.

For people using OpenClaw on longer coding tasks: how do you keep the next session grounded when the current one gets messy? I mean the point where the chat has old attempts, half-abandoned ideas, files that changed, and things the agent should not retry. Do you keep a plan.md, git diff, commits, scratchpad, repo notes, or some kind of handoff prompt? The handoff format I keep seeing from other AI coding users is something like: - current goal - files touched - what failed - what is known true - decisions made - what not to touch - next smallest test Curious what OpenClaw users actually do in practice.
Original Article

Similar Articles

Do agents.md files help coding agents?

Hacker News Top

This paper evaluates whether repository-level context files like AGENTS.md or CLAUDE.md improve coding agent performance, finding that LLM-generated context files offer little benefit and may reduce efficiency, while developer-written files are better but still not clearly advantageous.

AI coding agents need a company-wide AGENTS.md

Reddit r/AI_Agents

The article proposes that organizations adopting AI coding agents should create a company-wide AGENTS.md file, similar to a human onboarding doc, to standardize agent behavior and context.

@DivyanshT91162: https://x.com/DivyanshT91162/status/2057692858501804435

X AI KOLs Timeline

Andrej Karpathy's observations on AI coding agent behavior led to the viral CLAUDE.md file, which provides 4 behavioral rules for AI agents and became one of the fastest-growing repositories on GitHub, signaling a shift from AI intelligence to AI discipline in coding.