This solves a big issue for existing CLI agents, which is session persistence for users working from their own machines. With claude code, you usually start it

This solves a big issue for existing CLI agents, which is session persistence for users working from their own machines. With claude code, you usually start it from your own local terminal. Then you have access to all the code bases and other context you need and can provide that to the AI. But when you shut your laptop, or have network availability changes the show stops. I've solved this somewhat on MacOS using the app Amphetamine which allows the machine to go about its business with the laptop fully closed. But there are a variety of problems with this, including heat and wasted battery when put away for travel. Another option is to just spin up a cloud instance and pull the same repos to there and run claude from there. Then connect via tmux and let loose. But there are (perhaps easy to overcome) ux issues with getting context up to that you just don't have if it is running locally. The sandboxing maybe offers some sense of security--again something that can be possibly be handled by executing claude with a specially permissioned user role--which someone with John's use case in the video might want. --- I think its interesting to see OpenAI trying to crack the Agent UX, possibly for a user type (non developer) that would appreciate its capabilities just as much but not need the ability to install any python package on the fly.