Claude Code Subagents: A Researcher, Writer and Checker Team Checked
By Matt Cullerton, founder of Mavric and Apso
Professor Glitch (@pro.glitch) proposes a three-agent Claude Code team: a researcher that writes a facts page, a writer that drafts from it, and a checker with a written checklist. Most of the reasoning matches Anthropic's January 2026 article on multi-agent systems, including the 3 to 10 times token cost and the risk of a checker that passes work too easily. The video overstates Anthropic's position on file handoffs, and several of its product claims have no source.
Why not five agents named by job title?
The video warns against "5 BOTS NAMED BY JOB TITLE" all talking to each other. It says "Anthropic tested that kind of setup. It lost context at every handoff and spent more tokens coordinating than working," and "Teams of agents can use three to 10 times the tokens for the same job."
Anthropic's article "Building multi-agent systems: When and how to use them," dated January 23, 2026, supports all three points. It says multi-agent implementations "typically use 3-10x more tokens than single-agent approaches for equivalent tasks." It describes teams that "suffered from lost context at each handoff," and an experiment with role-based agents in which subagents spent more tokens on coordination than on the work.
Anthropic's June 13, 2025 research-system post gives different numbers (about 4 times the tokens of chat for agents, about 15 times for multi-agent systems). Those are measured against chat, not a single agent, so they should not be mixed with the 3 to 10 times figure.
The three-agent setup
The video's alternative is to split agents by what they read, not by job title. A skill file shown on screen runs them in order:
- The researcher saves a facts page per client to
handoff/. - The writer reads the facts page and saves a draft to
handoff/. - The checker reviews the draft. Failures go back to the writer, up to two rounds. If it still fails, the draft moves to
review/with a flag.
Does Anthropic recommend file handoffs?
Not in the article the video cites. The video says "Anthropic recommends exactly that, so nothing gets lost in a game of telephone," referring to handoffs through files in a shared folder. The January 2026 article uses the telephone-game image for information degrading across handoffs, but it does not discuss files as the handoff method.
The closer match is the June 2025 post, which describes subagents that store work externally and pass "lightweight references" back to the coordinator. That shows Anthropic has used pointer handoffs, which is weaker than a recommendation.
Does a Claude Code subagent start blank?
Mostly. The video says "a sub agent starts blank. It doesn't see your chat," so its instructions must go in its job file or on the page it receives. The Claude Code subagents documentation says subagents "don't see the parent conversation by default" and start with a fresh context window.
"Blank" is slightly too strong. A regular subagent starts with its own system prompt, the delegation message, CLAUDE.md files, a git status snapshot and any skills listed in its skills field. A fork is the exception and inherits the parent conversation.
Can you limit a subagent's tools and model?
Yes. The docs say subagents inherit the main conversation's tools unless restricted. tools is an allowlist and disallowedTools is a denylist. A researcher "that can't change anything" needs a read-only list, and Bash should stay off it because Bash can change files.
The model field accepts sonnet, opus, haiku, fable, a full model ID or inherit. That supports the video's advice to "put the researcher and the checker on a cheaper model." The docs name model routing as the main cost control.
How do you stop a checker from passing bad work?
Give it concrete criteria. The video says a checker told only to "make sure it is good" fails, and that "the checklist is the whole job." The January 2026 article names "marking outputs as passing without thorough testing" as the most significant failure mode for verification subagents. Its fixes are concrete criteria, thorough checks and explicit instructions to run the full set.
The video credits the name "the early victory problem" to Anthropic, but that phrase does not appear in the article.
Can Claude Code be stopped from sending without asking?
The video says a line in a job file saying "never send" is not enough, and that viewers should set a rule to "ask me before sending anything on every app."
Claude Code's auto mode docs support the warning. Explicit ask rules are evaluated before the classifier and "always force a permission prompt, even in auto mode." The docs also say a boundary stated in conversation, such as "don't push until I review," can be lost when context is compacted, and they recommend an ask or deny rule instead.
Ask rules are patterns on specific commands, such as Bash(git push *) and Bash(gh pr create *). No documentation shows a plain-English request turning into a rule that covers every app. You can print the rules in effect with claude auto-mode config.
What does it cost to run?
The video says "every employee runs on the same plan usage as you." The subagents docs confirm that subagent requests "count toward the same usage limits" as the main conversation. The docs add that each subagent's results return to the main conversation and take up its context.
The claim that three agents once a week "is fine on a normal plan" while ten running all day is not comes with no numbers. The video's Monday 7 AM schedule and its per-subagent usage display have no source in Anthropic's docs.
Bottom line
Anthropic's own writing supports the core advice: fewer agents split by what they read, a checker with concrete criteria, and model choice as the main cost lever. Anthropic has used reference-based handoffs but does not recommend this exact folder pipeline. A durable "ask before sending" guarantee needs ask rules on specific commands, not a sentence in a prompt.
Sources
- Building multi-agent systems: When and how to use them, Anthropic, January 23, 2026: the 3-10x token figure, handoff loss, coordination overhead and verifier failure.
- How we built our multi-agent research system, Anthropic engineering, June 13, 2025: the 4x and 15x token multiples and lightweight-reference handoffs.
- Create custom subagents, Claude Code docs: context isolation, tool allowlists, the model field and shared usage limits.
- Configure auto mode, Claude Code docs: ask rules in auto mode, pattern limits and conversation-stated boundaries.
Published November 12, 2026. Based on a TikTok by @pro.glitch. Full video notes (markdown)