Carousel Studio

Jey

@Jeyxbt

> One Claude talks to you. Five more can be working behind it, on five different jobs, and you never see a single one.

Apply Image

Jey

@Jeyxbt

Those five are sub-agents. A sub-agent is a second Claude the main chat hires for one job, runs in its own window, and never lets near your conversation. Its own context window. Its own model. Its own permissions. Running in parallel. It does the messy work somewhere else and hands back one clean answer. That gap is the whole game.

Jey

@Jeyxbt

Point five of them at the same draft. One reads it as a complete beginner. One as a software engineer. One as a business owner. One as a publisher. They run at the same time, in separate windows, each with its own lens, and the main chat just collects what comes back. Five full reviews off one prompt, and your context never fills up.

Jey

@Jeyxbt

The main chat is the orchestrator. It is the only thing that talks to you. Everything else is a worker it spins up and points at a job: go read these files, go research this, go roast this plan. The worker does the job in its own session and reports back. Sub-agents answer to the orchestrator, not to you, and not to each other.

Jey

@Jeyxbt

Here's the part almost nobody gets right. The win was never that Claude does more work. It is that the heavy work stops happening in the window you are sitting in.

Jey

@Jeyxbt

---

Jey

@Jeyxbt

# First, the receipt that makes the rest matter

Jey

@Jeyxbt

A reviewer sub-agent in one real run burned 22.8K tokens reading a plan and tearing it apart. What came back to the main session was a few lines. The main context never saw the 22.8K. It saw the verdict.

Jey

@Jeyxbt

That is the mechanic. Your main window fills as you work, and the more it fills, the more polluted it gets, and the dumber the model runs for the rest of the chat. A sub-agent sidesteps that. It wakes with a clean window, does the heavy reading in its own session, and slides back only the part you needed.

Jey

@Jeyxbt

Here is the same job, both ways:

Jey

@Jeyxbt

<b>WITHOUT a sub-agent </b>Main session reads 300 pages → 22.8K+ tokens land in main context Context now polluted, the model gets dumber for the rest of the chat All of it runs on Opus pricing <b>WITH a sub-agent </b>Haiku worker reads the 300 pages in an isolated window Returns 3 facts to the main session Main context stays clean. Opus stays sharp. Bill drops.

Jey

@Jeyxbt

Now put the economics on top:

Jey

@Jeyxbt

<b>THE FLEET ECONOMICS </b> Main session (orchestrator) &gt; Opus &gt; talks to you, plans, decides Research sub-agent &gt; Haiku &gt; reads 300 pages, returns 3 facts Test-writer sub-agent &gt; Sonnet &gt; writes the suite, returns the diff Doc-writer sub-agent &gt; Haiku &gt; drafts the README, returns the file Smart boss on the expensive model. Cheap workers on the cheap ones.

Jey

@Jeyxbt

You don't run Opus to read a 300-page report and pull three numbers. You send Haiku. It burns its own context, returns the summary, and Opus stays sharp for the calls that actually need it. <b>The win was never "Claude does more." It's that the expensive thinking and the cheap reading stop happening in the same window.</b>

Jey

@Jeyxbt

---

Jey

@Jeyxbt

# Built-in agents, custom agents, and the one file between them

Jey

@Jeyxbt

Those five personas were not custom anything. They were the built-in general-purpose agent, prompted five different ways. Claude ships with built-in agents. A research one fires on its own when you ask it to dig through a codebase or pull facts off the web. For a one-off, that is the right tool, and you've probably watched it kick in without asking.

Jey

@Jeyxbt

A custom sub-agent is something you write. And it is smaller than people expect: a single Markdown file with YAML front matter, sitting in <b>.claude/agents/.</b> Structurally it is almost the same object as a skill file. The only real differences are the clean context window, the parallel run, and the model it sits on.

Jey

@Jeyxbt

<b>Here is the whole thing:</b>