I’m in New York. My builds are home, on a laptop I’m nowhere near.
A week ago that was the whole problem. The session, the running conversation I keep open with the AI tool I use to build my software, lived on that one machine. Step away and I went dark. The work would finish and wait, or hit a wall and sit there until I got home. A trip meant losing days. Sometimes it meant coming home to a surprise.
So before this trip, I gave the agents one thing to solve. Not a feature. The problem behind the work: I never want to go dark on a build again.
They built it. One session per product, each one kept running, each one I can reach from my phone. I don’t have to be at the desk to check on the work or to steer it — I can pick a build back up from anywhere and point it at what’s next.
Now I’m on the train. I take out my phone and check a build. It’s mid-task. I see where it got to, give it a nudge, and put the phone away. It keeps going without me in the room.
One thing I made sure of: reaching it from my phone does not mean it is open to anyone else. The way in is locked to me. And what I can do from out here is steer, not gamble. I can nudge a build, point it at the next thing, read where it got to. The calls that touch anything real still wait until I am the one making them.
That’s the win. Being away stopped being a risk.
Learnings
The trip is what made it obvious. As long as a build only lived on the laptop in front of me, being away was a cost I was carrying without naming it. The fix wasn’t a smarter agent or a better feature. It was making every session continuous and reachable, so stepping away stopped costing me anything. A trip is just a place I check in from now.
For anyone building with these tools: the unlock isn’t the agent getting cleverer. It’s a session you can leave running and pick back up from your pocket.