<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How I Run AI Agents in the Cloud Without Leaving Claude Code (with Aether)</title><link>https://devopstoolkit.live/ai/how-i-run-ai-agents-in-the-cloud-without-leaving-claude-code-with-aether/index.html</link><description>I run AI agents on a machine that does nothing else. Not my laptop. A dedicated box, sitting in the corner, whose entire job is to run agents while I get on with something else. It’s a good setup, and it’s cheap. I paid for that box once. Renting something equivalent by the month would have cost more than the box did within a few months, and then it would have kept on costing.
It also has a ceiling. Not a ceiling on how many agents I can have open, though. The number that matters is how many of them are compiling, running tests, or otherwise doing real work at the same moment. Once that gets to five or six, they start fighting each other for CPU, memory, and disk, and everything grinds. Or it breaks completely.
So what do we do when we want to run more agents than the laptop or the server they’re on can handle?
The obvious answer is to buy a bigger machine. I don’t want to buy a bigger machine. I hit that ceiling maybe twice a week. Most days four or five of them are actually building anything at once, and buying hardware that sits idle six days out of seven to cover the seventh is exactly the mistake we spent a decade learning not to make with servers.
The other answer is the one we landed on with servers: keep the steady state on hardware you own, and rent the overflow when you need it. That works for agents too. What’s much less obvious is how you keep control of the rented ones, because the moment your agents are somewhere else, most tools want you to go and look at them somewhere else too. In a browser. In their dashboard. Not in the agent you actually use.
And I’m not switching. I use Claude Code. I use OpenCode. I’ve put real time into getting good at both, into the prompts, the skills, the muscle memory. If you want me to drop all of that and work inside your web interface instead, it had better be bloody spectacular. Not adequate. Not a reasonable alternative. Better than what I already have, or I’m not moving. A dashboard with a list of tasks on it is not a reason to abandon the tool I live in all day. It’s a reason to close the tab.
That’s what I wanted to find out. Whether I can borrow somebody else’s machines without giving up the thing I actually work in. The answer turned out to be mostly yes, and the “mostly” is the interesting part.</description><generator>Hugo</generator><language>en-us</language><lastBuildDate/><atom:link href="https://devopstoolkit.live/ai/how-i-run-ai-agents-in-the-cloud-without-leaving-claude-code-with-aether/index.xml" rel="self" type="application/rss+xml"/></channel></rss>