06-reference

indydevdan claude code 2 0 agentic coding

Sun Apr 19 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: IndyDevDan YouTube ·by IndyDevDan
indy-dev-danclaude-code-2-0claude-agent-sdkscout-plan-buildchained-slash-commandsauto-compact-bufferadwdedicated-agent-deviceafk-agentsr-and-d-frameworkcore-fourharness-engineering

IndyDevDan — Claude Code 2.0 Agentic Coding: No, other agents aren’t even close

Why this is in the vault

28-minute Claude Code 2.0 release walkthrough where Dan demonstrates two new platform capabilities (chained custom slash commands; the Claude Agent SDK migration) and surfaces one anti-feature (auto-compact buffer). The vault keeps it because it contains a specific tactical recommendation that affects every Claude Code user: turn off auto-compact-buffer (/config show compact false) to recover ~22% of context window currently being silently reserved by default. This is the kind of small operational finding that has compounding effects across long sessions and that nothing else in the vault has documented. Also the canonical demo of the scout-plan-build chained slash command pattern (composable agentic prompts via /scout-plan-build) and the AFK agents pattern (out-of-loop work on a dedicated agent device while in-loop work proceeds locally). Dated October 6 2025, this is the earliest public demo of chained slash commands in the IndyDevDan corpus and is the canonical artifact for that capability.

Core argument

  1. Claude Code 2.0 introduced chained custom slash commands — /scout-plan-build is composed of /scout, /plan-with-docs, /build. This is a structural change: agentic prompts are now composable. Prior to 2.0, slash commands were leaf nodes; now they can call other slash commands. Implication: the prompt engineering layer becomes a directed graph rather than a flat list.
  2. The /scout step is the structural answer to context-bloat in the planner. Scout delegates file-searching to four parallel sub-agents (Gemini Lite, Codex, Gemini Flash, Haiku) — multi-vendor specifically to get diversified perspectives, not aligned ones. The planner reads the scout’s relevant-files output and never burns its own context on file discovery.
  3. R&D is the only context-management framework: Reduce and Delegate. Anything that can be moved out of the primary agent’s window MUST be moved out. Scout reduces the planner’s context; ADWs (AI Developer Workflows) reduce the orchestrator’s context.
  4. Even with R&D, single primary agents will hit 51% context usage on real work. Dan’s demo of migrating an 8-app codebase to the Claude Agent SDK consumed half the primary agent’s window. ADWs are the structural escape — separate fresh agents per workflow phase.
  5. Auto-compact buffer is silently eating 22% of every Claude Code session’s context window. The default-on /config compact true reserves space for an automatic context summary that may never trigger. Recommendation: turn it off (/config compact false) for any session where context is precious.
  6. AFK agents on a dedicated agent device are a parallel-work multiplier. Dan demonstrates running an out-of-loop pipeline (build OpenAI realtime prototypes) on an M4 Mac Mini while in-loop work (SDK migration) proceeds on the primary device. Sleep-60s-check-status pattern from the local agent. The dedicated device is database-backed for full traceability.
  7. The Core Four (context, model, prompt, tools) applies at every agent level. The primary agent has Core Four; each sub-agent has Core Four; each AFK agent has Core Four. Engineers must always observe what their agent can see — what is the agent’s perspective at this moment.
  8. Other agentic CLIs (Codex CLI, Gemini CLI) are not close to Claude Code 2.0. Specific capabilities Dan claims exclusive: chained slash commands, sub-agent fan-out with multi-vendor models, custom output styles, the Claude Agent SDK polish. “You can’t be close to the leader when you just copy their feature set.” The vault should hold this as Dan’s stated bias and validate independently.

Mapping against Ray Data Co

Open follow-ups

Sponsorship

The video closes with a substantial pitch (~5 min) for Tactical Agentic Coding course — the Building Specialized Agents codebase is gated behind Agentic Horizon (paid extension). Dan’s exclusivity claim about Claude Code aligns with his course being built on Claude Code; if Codex CLI or Gemini CLI could replicate the pattern, the course’s exclusivity premium would erode. Per RDCO’s bias-flagging discipline: the technical findings (auto-compact buffer, chained slash commands, AFK pattern) are testable and reproducible from the public video. The course-aligned claims (exclusivity over Codex CLI / Gemini CLI) require independent validation before the vault can cite them as authoritative. The vault should not buy the course; it gets the patterns free and tests the exclusivity claim independently.