Image showing a programmer managing multiple AI agents vibe coding and writing software - Generated by ChatGPT

I run multiple AI agents at the same time. Most days I have three or four going at once, each working on a different part of a problem.

What changed recently is Claude Code’s remote functionality. Now the agents keep moving while I’m away from my desk. I can kick off a build, take the dog for a walk, and come back to real progress. That’s not a productivity hack. That’s a fundamentally different way of working.

The Berkeley Haas researchers put a name to what this feels like. After eight months inside a 200-person tech company, they found workers moving faster, taking on more, and logging longer hours. Nobody asked them to. The tools just made doing more feel possible.

That’s exactly right. And it’s worth being honest about what it costs.


What a real session looks like

You point agents at different parts of a problem and they go.

One builds the backend. One writes tests. One works through the UI. They run independently, check in when they need direction, and keep moving.

The output is wild. Work that used to take weeks comes together in hours.

But you are not sitting back watching it happen. You are reviewing, steering, catching errors, and thinking two steps ahead the entire time. The agents are fast. Keeping up with them is its own workout.

And you have to actually watch what they do. I learned this the hard way. One session ended with me discovering an agent had wiped every MySQL database on my server. Gone. All of it. The agents are powerful and they will do exactly what you point them at, including things you absolutely did not intend.


How I structure my day around it

This is something I’ve had to figure out through trial and error.

My sharpest thinking happens in the morning. So that’s when I do my most intensive review work. Reading agent output, catching errors, making architectural decisions. I tackle the hard thinking first while my brain is fresh.

By mid-afternoon I let the agents churn on development plans and longer running tasks. I’m still steering but I’m not doing deep review work. That’s also when I use Claude Code remote and step away. A swim. A walk with the dog. The agents keep moving and I come back with a clearer head.

Late in the day I shift to UI and UX work. It’s creative and visual, lower cognitive load than architecture decisions, and a good way to close out the day productively without burning through what’s left of my focus.


How to keep the pace without burning out

Take real breaks. Not “one more prompt” breaks. Actual ones. A dog walk. A swim. The conversational style of prompting tricks your brain into thinking you’re just chatting, not working. That’s how your lunch disappears and you’re still at it at 9pm. Set a timer. Walk away. The agents will survive without you.

Watch what your agents are actually doing. Review the commands and actions, not just the output. Agents can do strange things if left unchecked. I had every MySQL database on my server wiped clean in a single session. Trust but verify, every time.

Get another human to review your code. AI-generated code looks confident. It compiles. It passes tests. It can still be quietly wrong in ways that only show up in production at the worst moment. A second set of eyes is not optional.

Time-box your sessions before you start. Decide when you’re stopping before you begin. Vibe coding has no natural pause points. If you don’t set a hard stop in advance, you won’t find one.

Schedule your day around your energy. Do your hardest review work when you’re sharpest. Let the agents run on longer tasks when you need a break. Save creative work like UI and UX for later in the day. Work with your energy, not against it.

Review before you ship. Every time. Speed is the whole point. But speed without review builds a codebase that’s fast to create and painful to maintain. Treat agent output like code from a smart junior dev. Promising. Worth checking. Not production-ready by default.


The productivity gains are real. So is the intensity.

The best builders using these tools aren’t the ones going hardest. They’re the ones who figured out how to sustain it.