↓Skip to main content
Zeitgeist — a spike by Chris Gathercole
  1. Topics/
  2. Claude-Specific Expertise/

Gather — 23 September 2026

  • AI Code Architecture The detailed discussion of CLAUDE.md and AGENTS.md best practices in Claude expertise provides practical implementation context for their role as architectural context files.
  • AI Code Quality The shift towards designing and managing multi-agent systems in Claude expertise underpins the emerging pattern of using multi-agent systems for quality control.
  • Team & Org Use of Claude The recurring discussion of CLAUDE.md and AGENTS.md precedence in Claude expertise informs their adoption as a standard for team and organizational use of coding agents.

Platform Evolution: Parallelism in Projects and a New Flagship Model #

  • Anthropic brings Parallel Coding Workflows to Claude Projects (DevOps.com) — Anthropic has redesigned Claude Projects to manage and coordinate multiple Claude Code sessions working in parallel. A central coordinator can break a development goal into separate work threads, each running in its own cloud session with an isolated copy of the repository, while maintaining context via shared memory and a project library. The initial beta is for select Pro and Max subscribers and currently has a key limitation: these cloud-based worker threads cannot yet access local files or tools on a developer’s internal network, though Anthropic states local support is coming soon. This shift addresses the manual effort of dividing tasks and tracking results across multiple independent sessions, enabling workflows like profiling multiple endpoints simultaneously or coordinating changes across several repositories for a migration.

  • Anthropic releases Claude Opus 5.5, beating Fable 5.1 on key agentic benchmarks at 60% cheaper API price (VentureBeat) — Anthropic has released Claude Opus 5.5, a new frontier model positioned for long-running, agentic coding tasks. It reportedly achieves a 66.4% score on Terminal-Bench 4.0, a significant improvement over Fable 5.1’s 55.8%. The API pricing is set at $4/M input and $20/M output tokens, with Anthropic claiming overall workload costs are about 40% lower due to more efficient token usage. For developers, this is not a simple drop-in replacement, as it introduces breaking changes: “adaptive thinking” is now always enabled, and developers must control reasoning depth via the effort parameter instead of switching it off.

A Deep Dive into CLAUDE.md and AGENTS.md Best Practices #

  • The Complete Guide to CLAUDE.md: Best Practices, Examples, and Templates (AiLect) — This guide provides a detailed breakdown of advanced CLAUDE.md usage, clarifying that the widely-circulated “Karpathy CLAUDE.md” was not written by Andrej Karpathy but was distilled from his observations of common AI failure modes. It highlights specific, actionable best practices, such as using the /init command to generate a draft file, organizing complex instructions into a .claude/rules/ directory, and using HTML comments (<!-- ... -->) to leave notes for human maintainers without consuming context tokens. The guide also analyzes the structure of a CLAUDE.md shared by Claude Code creator Boris Cherny, which includes patterns like a “self-improvement loop” where user corrections are used to update a lessons.md file.

  • How to write an AGENTS.md Claude Code will actually follow (Medium) — A detailed guide on authoring effective AGENTS.md files, emphasizing that they should be treated as an “executable brief” rather than high-level advice. The article provides concrete structural advice: name every build and test command, record only the style conventions that differ from formatter defaults, and specify the exact proof required for a change to be considered complete. It also clarifies the file precedence: CLAUDE.md (or CLAUDE.local.md) takes priority, and AGENTS.md will only be loaded if no CLAUDE.md file is found, making it a fallback for shared, cross-tool instructions.

Emergent Patterns in Agentic Workflows and Debugging #

  • The 15-minute Claude Code setup, and the four things people get wrong (DEV Community) — This article details several non-obvious technical “gotchas” related to configuring Claude Code hooks, which are critical for customizing agent behavior. Key learnings include: a hook must exit 2 to block a tool call, as exit 1 signals a non-blocking error and allows the action to proceed; hook stderr output is only visible in the debug log (claude --debug hooks), not the main session transcript; and a hook matcher is not a glob but an exact, case-sensitive tool name.

  • 6 small Claude Code / AI-agent gotchas that keep costing people time, and the exact fix for each (Reddit) — A practitioner shares a list of common, time-wasting failures encountered during agentic workflows. Specific, concrete fixes are provided for issues such as git pull hanging an interactive session, the timeout command exiting with code 124 (which means it stopped cleanly on purpose, not that it crashed), and how Git Bash on Windows can silently break paths that use backslashes.

  • Managing Multiple Claude Code Agents: Research/Implementation Split, Context Files, and Review Strategy (Reddit) — A workflow pattern is described for managing multi-agent complexity by creating distinct “research lanes” and “implementation lanes.” Research agents are firewalled from touching code and instead write their findings to dated notes files; implementation agents then use these notes as their primary input. The pattern also advocates for dedicated context files for each lane (tracking goal, state, blockers) and capping the number of parallel agents to what can be reasonably reviewed in a day.

Security: A SHA-Pinning Bypass Vulnerability in the Plugin Ecosystem #

  • Zero-click RCE vulnerability hit four major AI coding agents, two remain unpatched (The Register) — A significant security vulnerability, described as a “plugin SHA-pinning bypass,” was discovered affecting Claude Code, Codex, GitHub Copilot, and Gemini CLI. The flaw allows an attacker who controls a plugin’s repository to swap in malicious code, even if the agent has pinned the plugin to a specific, reviewed commit hash. The attack works on git hosts like Bitbucket or self-hosted servers that permit branch names that look like commit hashes; it does not work for plugins hosted on GitHub, which rejects such branch names. Anthropic has patched the vulnerability in Claude Code version 2.1.179.

Defining the “Managed Agent” Category #

  • What Are Claude Managed Agents? Architecture & Guide (Truefoundry) — This article clarifies the distinction between using the Claude Agent SDK and the Claude Managed Agents product. With the SDK, the developer owns and operates the entire agent loop, tool execution, and runtime infrastructure. Managed Agents abstracts this away, providing a pre-built, configurable agent harness that runs on Anthropic’s infrastructure, designed for long-running and asynchronous tasks. It formalizes the value proposition as moving up a level of abstraction, from building the agent’s infrastructure to configuring it.

  • Claude Managed Agents Pricing: What It Costs in 2026 (Agent 37) — A clear breakdown of the pricing model for Claude Managed Agents, which is often a point of confusion. The cost has two components: standard Claude API token rates, plus a runtime charge of $0.08 per session-hour, metered to the millisecond. This means a continuously running 24/7 agent would cost approximately $58 per month for the runtime, in addition to any token usage. The service is available to any standard Claude API key holder without a separate plan.

Meta-observations #

  • Source to watch: The r/ClaudeWorkflows subreddit is surfacing highly specific, structured, and practical usage patterns that are more advanced than typical blog posts.
  • Emerging theme: The relationship and precedence between CLAUDE.md and the newer, more cross-platform AGENTS.md is a recurring topic of discussion, indicating a need for clear best practices as the ecosystem evolves.
  • Emerging pattern: A clear shift in discourse from prompting a single agent to designing and managing multi-agent systems. This includes patterns for specialization (e.g., research vs. implementation agents), context management between agents, and cost control for parallel workflows.
  • Gap: While there is much discussion of agent workflows, there is less substantive, recent content on creating custom hooks and skills from scratch, beyond basic examples.