Claude Code Subagents: The 2 I Actually Kept (2026 Field Log)
Two weeks of pushing real work onto Claude Code subagents. The two I kept, the frontmatter line that actually decides delegation, and the gotcha that cost me an afternoon.
Tag
19 posts tagged.
Two weeks of pushing real work onto Claude Code subagents. The two I kept, the frontmatter line that actually decides delegation, and the gotcha that cost me an afternoon.
I lived on Claude Code Router for two weeks in 2026. Here is the per-task routing config I actually run, and where routing to cheap models quietly wrecks a session.
Claude Code can now drive a real browser: read the console, click through your app, fill forms, pull data. Two weeks of using it on live work, what it replaced, where it still hands the keyboard back, and the context-cost footgun nobody warns you about.
AGENTS.md vs CLAUDE.md is not a format war. A 2026 field log on running both files in one repo, why Claude Code ignores AGENTS.md, and the one-line import that fixed it.
The standalone /output-style command is gone as of v2.1.91, so most guides are stale. Here is the current way to switch styles, which of the four built-ins earn their place, and the keep-coding-instructions flag that quietly breaks custom styles.
A working reference: the five MCP servers I keep loaded in Claude Code after a year of daily use, the ones I removed, why every server costs context-window tokens, and the exact scope config that keeps the list short.
A config field log: the exact Claude Code statusline I run in 2026, the four fields that earn their place, the ones I deleted, and why the bar sometimes shows up empty.
A field note on Claude Code plan mode after months of daily use: when it saves me, when I skip it, three failure modes the listicles miss, and the exact habit I built around it.
Six AI coding agents sit in my dock in 2026, but I do not open all six every day. Here is the honest field log of which one I reach for when the task is a refactor, a chore, or a tight edit loop, plus the routing rule that keeps surviving.
I ran Claude Code dynamic workflows daily for two weeks on a real Next.js project. Where the parallel subagents earned the token bill, where they quietly wasted it, and the four-question test I run before I type ultracode.
Claude Code memory is three things, and auto memory quietly remembered a workaround I never asked it to keep. My exact keep/prune split, plus a three-question test for what earns a slot.
A field note on Claude Code commands: which custom slash commands actually earned their place, which I deleted, and the 2026 question the listicles skip, when a command should have been a skill.