The Cockpit Only Flies on Claude

Last post I told you how I got my agent roster off Anthropic's per-token meter. So here's the obvious follow-up before anyone asks it: no, I didn't quit Claude. I moved the volume off it — and I still reach for Claude on the jobs that earn it, because the one piece of tooling I refuse to work without doesn't run on anything else.

Before you ask

My last post was about moving a whole team of AI agents onto cheaper models — Kimi Code for the daily roster, GLM-5.2 through Ollama Cloud for the critic. The math was the point: don't pay frontier per-token rates for work a cheaper model does just fine.

The fair question after a post like that is "so you dumped Claude?" No. I didn't cut it and I didn't go free-only. I dropped from the $100 Max plan to the $17 Pro plan — and I want to be precise about why, because it's not the story you'd assume.

The plain truth, stated flat

Let me say the thing the whole "save money on AI" genre tiptoes around: people use Claude because it has the best models. That's it. That's the reason half the tech world develops on Claude Code. If you've got the budget, you buy the best tool on the shelf and you don't overthink it — and for a lot of serious work, the best tool is still Claude.

I'm not the exception to that. I still reach for Claude's top models when the work earns them — the gnarly architecture call, the review that has to be right, the thing where a second-tier answer costs me more than the tokens ever would. Nothing in my last post was "Claude isn't worth it." The post was "I was paying frontier rates for a lot of work that didn't need frontier answers." Those are completely different claims, and I collapsed them on purpose here because the internet loves to hear the second one as the first.

The money, right-sized

Here's the actual mechanic. Anthropic's plans, roughly: Pro at $17/month, Max from $100/month. For a year I sat on Max, and I sat there for one honest reason — I kept hitting limits. When you run a lot of Claude Code, Pro's ceiling arrives fast, and the only lever is the jump to Max.

Then I moved the volume. Once the daily grind — the eight-seat roster, the wide work — ran on Kimi and Ollama Cloud instead of on Claude, my Claude usage collapsed to only the sessions that actually wanted Claude's models. And that usage fits inside Pro with room to spare. I didn't downgrade because Anthropic charges too much. I downgraded because I stopped asking Claude to do the work that was inflating my own bill. Right-sizing, not a protest.

So the honest headline isn't "I quit paying Anthropic." It's "I finally pay Anthropic for the right amount of the right thing."

The part I'd never give up: the cockpit

Here's what surprised me. When I trimmed Claude down to just the top-model sessions, I braced to lose the thing I'd quietly come to depend on. I didn't — because it comes with Pro, not just Max.

Claude Code has a pair of features — Remote Control and background sessions — and together they're the best-built version of "run my work from anywhere" I've used. The whole ritual is three commands inside a session:

/rename deborah-schema-review   # a name I'll recognize, not a hash
/remote-control                 # let my phone reach this one
/bg                             # cut it loose from this terminal

Each does one thing. /rename labels the session. /remote-control registers it so the Claude app on my phone can drive it — the session shows a QR code to scan, and after that it's live and in sync across terminal and phone. And /bg hands it to a background supervisor that keeps it running with no terminal attached at all.

Then comes the part I actually love. From any terminal — a fresh tab, another box, an SSH shell into Deborah from wherever I've wandered off to — one command shows me the whole fleet:

claude agents

One screen, every background session, grouped by what it's doing: Working, Needs input, Completed. Each row is a full Claude Code conversation still alive under the supervisor — peek at it, fire back a reply, attach for the whole transcript, then leave it running again. What sold me on the lot of it is the shape underneath:

It runs on my machine. Remote Control isn't cloud Claude — the session executes locally, against my filesystem, my MCP servers, my project config. Only the chat messages travel, over TLS, outbound HTTPS only. No inbound ports opened on my box. Files never leave.
It survives the terminal. A backgrounded session lives under a per-user supervisor process, not the shell that started it. Close the tab, let the laptop sleep — the work keeps going and picks back up on wake. Each session even isolates its file edits in its own git worktree, so parallel ones don't step on each other.
Two ways back in. claude agents from any shell that can reach the box, or the phone's Code tab for the remote-controlled ones — a labeled list with a green dot on whatever's live.

The engineering here is genuinely good, and it's Anthropic's. Short-lived credentials scoped to a single purpose, each expiring on its own. No open ports. The web and mobile surfaces are just a window onto a process that never left my desk. Somebody thought hard about the security model, and it shows.

And here's the part that reframed the whole "I moved off Claude" story for me: the cockpit only flies on Claude's own models. Remote Control needs Claude Code talking straight to api.anthropic.com under a claude.ai login. The moment you point Claude Code at another provider — exactly what I do when I run GLM-5.2 through Ollama Cloud, which redirects the API endpoint — Remote Control switches off. API keys don't unlock it either; it wants the subscription. So this isn't a feature I get to keep instead of paying for Claude's brains. I get it because I'm on them. The cockpit and the top models are welded together: when I want the one, I'm running the other.

That's not a complaint — it's the reason the whole arrangement holds. The jobs where I reach for the cockpit are the jobs I wanted Claude's best models for in the first place. The tooling being locked to the models just means the seat I keep for Claude is a seat that pulls double duty: best answers and the best way to drive them from anywhere.

Kick it off, then go live your life

This is the workflow I can't imagine giving back. I start a Claude session at my desk on something that's going to take a while — a long review, a big refactor, a data job — and then I leave. On the couch, in the truck, in line somewhere, I open the Claude app, tap Code, and there's my session in the list with a little green dot next to it. I steer it from my thumb.

And I don't have to babysit it. Claude Code will push a notification to my phone when a long job finishes or when it hits a fork it needs me to settle. I can even ask for it in the prompt — notify me when the migration finishes — and get pinged when it lands. A backgrounded session plus a phone in my pocket means "start it and walk away" is a real workflow, not a demo.

One honest limit, because it matters: this whole thing lives on my machine. The supervisor that keeps those background sessions alive runs on Deborah — so if the box is powered down or off the network, the fleet's asleep too. That's the trade for keeping everything local instead of handing it to somebody's cloud, and frankly it's the trade I'd pick every time.

And here's the admission that follows straight from it: when I know I'm going to want to leave the desk and keep working, I have to start that session on Claude. Not because the cheap models can't do the work — they can — but because they can't come with me. Kimi and the Ollama-Cloud models are brilliant while I'm sitting in front of the terminal; the moment I stand up, they stay behind. So the decision of which brain to reach for isn't purely "how hard is this problem" anymore. Half the time it's "am I going to want to walk away from this one" — and when the answer is yes, the choice makes itself. That job goes to Claude, because Claude is the only one that follows me to the couch.

Why this still isn't renting a mind

If you read my last post you know the line I keep coming back to: a mind you rent is a mind someone else can switch off. So it's fair to ask how driving Claude from my phone squares with that.

It squares cleanly, and this is the part I actually love. Remote Control is the inverse of rented compute. The model call still goes to Anthropic — I'm paying for the brain, same as always — but the session, the files, the tools, the whole working context, all of it stays on Deborah. I'm not shipping my work to someone's cloud to reach it from the road. I'm reaching back into hardware I own, through an encrypted pinhole, from anywhere. Remote access to my own stack is the most on-brand thing I could ask a tool to do. Cloud for the brain, local for everything around it — the same bridge I've argued for all along, just with a phone on the far end of it.

The one thing I wish

I'll be straight about where this leaves the cheaper tools I love. Kimi Code is my daily driver and I'm not walking that back — it does the bulk of the real work and it does it well. But it doesn't have this. No Remote Control, no phone-in-the-loop, no push-when-it-lands. If it shipped that, I'd lean on it for even more than I already do.

That's not a knock on Kimi — it's a measure of how far ahead Anthropic shipped on this particular thing. Remote Control landed as a research preview and it already feels more finished than most products' 2.0. I hope the whole ecosystem chases it, because everybody driving sessions from their pocket would be a better world to work in. But today, if you want it, there's one place to get the good version of it, and Anthropic built it.

Where this actually nets out

So here's the shape of my stack now, without the spin:

Cheap models carry the volume — the roster, the wide work, the third and fourth opinions. Kimi and Ollama Cloud, for pennies on the frontier dollar.
Claude carries the work that earns it — the sharpest calls, on the best models around, which are still Anthropic's. I pay for that gladly.
And I drive the whole Claude side of it from my phone, on the $17 plan, because I stopped feeding it the volume that used to force me up to $100.

That's the same thesis as last time, just told from the other end: cheap where I can, the best tool where it counts. The version of "saving money on AI" that ages well isn't refusing to pay for quality — it's refusing to pay quality prices for quantity work. Move the quantity, keep the quality, and the bill and the toolset both come out better than where you started.

The best models still win. I'm just careful now about which jobs I hand them — and grateful that the tool wrapped around them lets me run those jobs from a phone on my couch, against a machine that's still sitting on my own desk.

Pages

Wednesday, July 8, 2026