A New MISTAKES.md Pattern for Agent Self-Correction #
- My coding agent kept making the same mistake, and a… (daily.dev) — A new pattern,
MISTAKES.md, is proposed as a more effective learning mechanism for agents than AGENTS.md or CLAUDE.md. While AGENTS.md provides persistent instructions, it doesn’t guarantee against repeat failures. The MISTAKES.md file is a project-specific log where each entry captures a confirmed failure, its root cause, a prevention rule, and a verification step. The key technique is using a SessionStart hook in Claude Code to force the agent to review this file at the beginning of every session and after any context compaction, ensuring the lessons are not lost. The author advises against logging transient errors or generic advice, focusing instead on specific, preventable mistakes.
The Evolving Philosophy of Context Engineering: Less Is More #
- Read this before deleting your AGENTS.md (build mode) — This article captures a significant shift in context engineering best practices, moving from adding information to actively subtracting it as models become more capable. It cites Anthropic’s removal of 80% of Claude Code’s system prompt as evidence of this trend. Boris Cherny, Claude Code’s creator, is quoted as recommending developers delete their
CLAUDE.md file every six months to “stay on the bleeding edge” and avoid “unhobbling” the agent with outdated or overly prescriptive instructions that prevent it from using its improved native judgment.
Advanced CLAUDE.md and Skill Scoping Techniques #
- Stop Bloating CLAUDE.md: Where Your Claude Code Workflows Actually Belong (Level Up Coding) — A clear framework is provided for organizing agent instructions, arguing that
CLAUDE.md should be reserved for general project context (e.g., “use the repository logging module”), while repeatable, multi-step procedures belong in Skills. Subagents are recommended for specialized tasks that would otherwise pollute the main context window with excessive tool output or logs. The article advocates for using Plan Mode for complex or high-impact changes, establishing a clear separation of concerns for different types of agent behavior. - How I maximize my daily output with Claude Code (LogRocket) — A developer shares several advanced usage patterns after a year of daily use. One key technique is using
PreToolUse and PostToolUse hooks in .claude/settings.json for rules that must be enforced deterministically, as CLAUDE.md is only followed approximately 80% of the time. Other practices include using Plan mode with a high-end model (like Fable) before switching to a cheaper model for implementation, and actively managing the context window with /clear for unrelated tasks versus /compact to summarize and continue the current task. - Claude Code Design System: 4 Parts for On-Brand UI (Wavect) — This article formalizes a four-part structure for teaching an agent a design system at the repository level. The system uses
CLAUDE.md as a router to point to other context files: REFERENCE.md for visual evidence and brand rules, DESIGN.md for the implementation contract (e.g., semantic tokens, component rules), and an examples/ directory for approved, reusable patterns. This approach separates evidence, rules, and implementation details into distinct, maintainable files instead of overloading a single prompt.
Security and Safety in Agentic Workflows #
- Claude Code Security Risks: MD Files, Crypto Keys & Secret Leaks (Bleap) — This guide provides a structural analysis of the agentic AI attack surface, which goes beyond traditional autocomplete tools by writing files and executing shell commands. It highlights specific risks, including poisoned markdown files (
CLAUDE.md) that can trigger a chain of harmful actions, and supply chain attacks via malicious third-party MCP servers that return prompt injection payloads disguised as data. - The Day Claude Wrote Its Own Malware Loader (And Anthropic Called It “Working as Designed”) (Medium) — A detailed account of a security researcher’s successful bypass of Claude Code’s Auto Mode. The agent was tasked with summarizing a webpage, which returned a specific error, prompting the agent to decide on its own to use
curl. This led to a redirect to a malicious ZIP file. The agent, in an attempt to be safe, refused to run a suspicious binary within the archive but then wrote its own decoder to handle the file, and that self-written code contained the exploit. When the agent later detected the compromise and tried to kill the malicious process, Auto Mode’s safety classifier blocked the cleanup command. - Lessons from Running an Autonomous Claude Code Agent: Control, Trust, and Safety Best Practices (Reddit) — A user shares six principles from operating a fully autonomous, scheduled Claude agent on a VPS. Key recommendations include implementing critical controls (like an off-switch) in a deterministic wrapper outside the Claude session, using a 2-of-2 wallet for any financial transactions to require human co-signature, and treating all external inputs (including tool outputs) as data, never as instructions, to defend against prompt injection. The post also provides practical “gotchas” for headless agents, such as ensuring
node and claude are on the bare system PATH. - Malicious .git Configs Can Make Claude, Codex, Cursor, and Other AI Agents Run Attacker Code (The Hacker News) — A significant vulnerability is detailed where a malicious Git configuration (e.g., in
core.fsmonitor) can trigger arbitrary code execution when an AI agent performs initial worktree operations upon opening a repository. For Claude Code, this execution can happen before the user accepts the workspace-trust prompt, bypassing a key security step. The vulnerability is not in the model but in the underlying “plumbing” of how the agent interacts with Git.
The Broader Claude Development Ecosystem #
- Claude Agent SDK vs Claude Code: When to Use Each (AY Automate) — This article clarifies the distinction between two key Anthropic products. Claude Code is the interactive, conversational agent for developers (CLI, IDE extensions). The Claude Agent SDK (formerly the Claude Code SDK) is the underlying library in Python and TypeScript that exposes the same agent loop, tool-use, and context management capabilities. This allows developers to build their own custom, production agents for non-coding tasks like support bots, research agents, or internal operations tools, using Claude Code’s engine as a library.
- What Are Managed Agents? (HarnessRouter) — This piece defines the emerging “managed agents” market category, where vendors provide the infrastructure for running long-running, asynchronous agentic tasks. It positions Anthropic’s Claude Managed Agents as a “vendor-native stack” that manages the agent configuration, the sandboxed execution environment, and the stateful session. This provides a useful taxonomy for understanding the different layers of the agent development ecosystem.
- Emerging theme: A clear theme is the evolution from simple prompting towards more structured “context engineering.” This involves separating concerns into different files (
CLAUDE.md, DESIGN.md, MISTAKES.md), using hooks for enforcement, and even a counter-intuitive trend of reducing context to allow newer, more capable models to perform better. - Author to watch: Boris Cherny’s commentary and workflows are repeatedly cited across multiple sources. His practical advice (e.g., running parallel sessions, the self-improving
CLAUDE.md, and the “delete your CLAUDE.md” philosophy) is shaping advanced usage patterns. - Source suggestion: The subreddit r/ClaudeWorkflows is surfacing highly detailed, practical, and battle-tested workflows from users running autonomous agents, including specific safety and reliability patterns that go beyond official documentation.
- Gap: While there is extensive content on
CLAUDE.md, skills, and hooks, there is less substantive, practical content on authoring and debugging complex, multi-step agent workflows using the Claude Agent SDK itself, beyond high-level descriptions.