Notes from the control plane

What we're learning running agents in production.

Close reads of agent systems that actually run: somebody else's taken apart to see what holds it up, or one of ours with the receipt attached.

21 Jul 2026Product

The agents finished hours ago. They're waiting for you.

Agent output piles up faster than anyone can review it, so every item looks equally urgent until you've read it. Review by exception is the way through.
21 Jul 2026Engineering

Seven jobs every DIY agent harness ends up owning

Teams running agents overnight keep rebuilding the same surrounding machinery. The hard part is the state those pieces have to share.
17 Jul 2026Operations

Anatomy of a $6,000 night

A close read of the r/ClaudeAI incident: where the money leaked, and the moment a hard cap would have turned the bill into a $20 decision.
12 Jul 2026Engineering

Cloudflare reviews code with seven models for $1.19 a review

Their write-up of the system is a blueprint: a panel sized to risk, judged by a coordinator, metered to the cent. Here's what each decision teaches.
12 Jul 2026Engineering

Ramp's agent drafts 30% of their merged frontend and backend PRs. It took five systems.

Follow one pull request through Inspect's machinery and you can see why it works, and what it costs to keep running. A close read of Ramp's write-up.
12 Jul 2026Engineering

Seven models reviewed the same change. They disagreed.

We ran one merge request through a panel of seven models, frontier and open-source, each reviewing blind. The disagreement turned out to be the useful part.
12 Jul 2026Engineering

1,300 agent-written PRs a week, and almost none of the work is the model

Stripe published how their coding agents work. The interesting part is the infrastructure around the model, and it reads as a checklist for any engineering team.