Pretty sure on advisor it needs to send the entire context to another model. The cost is mitigated a bit because there would be few output tokens from the advisor model normally.

Orchestrator seems to automatically delegate things to subagents as required is my read of it. This should be fine for caching.

> This should be fine for caching.

When launching a swarm of smaller models, they can theoretically share cache amongst themselves, but not with the larger model (that already has it cached). They have different architectures.

Further, it wouldn't really make sense for them to share the same cache anyway! The swarm, that is, they'd be working on independent things...

Yeah, the advisor mode does send the whole context, but you're only billed the cache input price for that, so either they just eat the cost, or they actually have something that makes it possible to move the cache between different models.

I have absolutely no clue how these things works, but could it be that all the newer models are actually just the same model, with looped transformers, so it's just about how many passes it does internally that decides if it's Haiku / Sonnet / Opus / Fable?

I might have misread the article a little bit, as you say, this is just workflow orchestration with subagents. Anthropic seems to think that this isn't the best approach anymore with their recent posts around subagent use and with the experimental advisor mode. So who knows.