This Week in AI Agents: The Router Won the Week
No flagship model shipped — instead we got routers that cut costs 68%, MCP growing up with a Ruby SDK and an Agents working group, and coding tools turning into model supermarkets.
No flagship model shipped between August 4 and 10. What shipped instead was the plumbing that decides which model you hit, where your agent runs, and whether your tools actually compose.
That plumbing matters more than the next benchmark bump.
###Routing beat raw intelligence
Cursor published how its Router works on August 6, and the numbers are worth reading twice. Auto Intelligence now delivers above Fable-level satisfaction at 68% lower cost — another 18% drop since Router launched July 22. Auto Balance beats Opus 4.8 at 41% lower cost.
The trick isn't a better model. It's Compass, a classifier that predicts task complexity from real production traffic, plus a learned map of which models are strong at what. Labs slice model families by price and speed; Cursor slices routing by task. If you're building agents, your margin lives in the router now, not the model call.
I run a similar pattern with per-task tool allowlists — same idea at a different layer.
###MCP grew up a little
The biggest protocol change landed just before this window — the July 28 spec killed Mcp-Session-Id and the sticky initialize handshake. Any request can hit any replica now. This week the ecosystem caught up:
- Ruby SDK 1.0 went stable August 5-6. First SemVer-stable API for Ruby. If you're a Rails shop, your excuse for not shipping an MCP server just expired.
- Agents Working Group chartered August 5 inside the spec repo. Not a spec change yet, but agents are getting first-class treatment, not just bolted-on tools.
- Centaur 2.0 shipped August 10 from Paradigm — self-hosted, multiplayer runtime rebuilt with granular permissions, company-wide context archival (Gmail, Granola, Slack), and MCP.
That last one sets up the week's real split.
###Managed vs. self-hosted
LangChain went the other direction. On August 7, Managed Deep Agents hit public beta on LangSmith — durable execution, memory, sandboxes, channels, evals, all hosted. Two days earlier they published the mirror image: an autonomous SRE agent recipe for Kubernetes that keeps a human approval gate for changes.
Two bets, same question: who holds the audit log and the credentials? LangChain says "give us your agents, we'll run them right." Paradigm says "run them yourself, with real permissions." Neither is turnkey yet.
A small bridge worth noting: Vibsync hit Hacker News August 8 — one MCP endpoint (mcp.vibsync.com) that gives Claude Code, Cursor, and Codex shared memory across sessions and machines. Still in free beta, but it nails the real pain: I'm not losing time to model quality, I'm losing it to agents re-doing research another agent already did.
###Coding assistants became supermarkets
GitHub resumed rolling out Kimi K3 in Copilot August 6, billed at provider list pricing. Not "Copilot picks for you" — you pick Kimi. Same week, OpenAI Codex cut eight releases including rust-v0.147.0 and a string of v0.148.0-alpha builds, and Claude Code quietly lifted its 200-subagent limit in an August 7 commit.
Different moves, same direction: the editor isn't the moat anymore. The moat is which models you can route to and how many subagents you can fan out. Microsoft Research even dropped Agentic Coding in the Wild on August 9 — a production trace study of Copilot at scale. We're finally getting telemetry instead of vibes.
###What I'd try next
Point one agent at a stateless MCP server and watch what breaks without session affinity. Then add any shared memory layer — even a dumb one. The router and the memory will teach you more about agent quality than the next model bump.
And if you're picking a framework this week, don't pick a model. Pick a control plane: who runs it, who audits it, and how you swap models when — not if — the router tells you to.