Considering the harness needs to be running how else would this work?
replyPretty easy these days with old school tools like tmux but more modern tooling like herdr [0] is really the path you'd want to take.
codex itself has a remote control mode that runs continuously. I wrote a systemd service to start it boot and interact with it via my phone.
replyBut Codex doesn't survive a reboot by default or a laptop going to sleep. Also, herdr is abstracted up a level from the agent, so you actually get more benefit by using Codex with herdr because herdr knows how to operate Codex, and other harnesses. So if you're using multiple Codex instances you can orchestrate them because each harness can talk to the others. You can still interact with Codex running in herdr via remote control (ideally you'd target your "orchestration" Codex instance). It just gives you way more power.
reply> Considering the harness needs to be running how else would this work?
replyyou can just make new sessions for each new task?
i tend to do this, or at least every so often.
replyi just give it a config (agents.md etc) to where it knows what's going on, or can figure it out
Codex remote control serve can run continuously.
replySometimes start a new chat in the phone app, sometimes just add to the main one. Both seem to work ok.
If I want the agent to wait for something I need to start a new chat in the iphone app.