I've recently had great success running codex in a regular qemu VM and using codex remote control to talk to it from my phone.

Honestly works extremely well as a personal assistant.

I can see why turning it into an API makes sense, just be aware you might not need to lock yourself in if you can setup your own VMs.

▲

pavo-etc 3 minutes ago | parent | next [-]

I've done something similar by running pi within an xmpp wrapper on my server, so I can talk to it from any phone or computer. Works super well.

▲

blfr 4 hours ago | parent | prev | next [-]

Yes, I do the same with Claude Code. Create an instance on the server for a project and then can create sessions from any device, close my laptop while claude code keeps working, etc. without losing the convenience of dedicated apps.

	▲	4 hours ago \| parent [-]
		[deleted]

▲

lukebuehler an hour ago | parent | prev | next [-]

The key here is that they are _not_ just turning "running codex on a VM" into an API. Their harness is running outside a VM, interacting with a VM when needed. See the diagram in their post. This allows them to scale the agent runs independently from the VMs. That's why they call it "managed Codex harness", it's a different version than what you run.

▲

bmurphy1976 2 hours ago | parent | prev | next [-]

I've been running Hermes inside a remote docker container connected to Slack bound to a Codex account. It's actually pretty great, I prefer this approach for a lot of things. Because it's in a Docker container I have 100% control over the configuration. It may do some crazy stuff, but I know it's not going to start exfiltrating my AWS SSO tokens or SSH keys from my laptop.

▲

kyxsc 4 hours ago | parent | prev | next [-]

Yep I run `claude remote-control` as daemons (systemd/launchctl) on whatever paths/repos I wanna be able to create a session from on-to-go.

Works really well and is a great use case for work laptops. Same shell, same memories, same sessions

▲

Havoc an hour ago | parent | prev | next [-]

May as well go for Hermes at that stage

▲

krashidov 5 hours ago | parent | prev [-]

Do you have 1 long running session?

▲

windexh8er 4 hours ago | parent | next [-]

Considering the harness needs to be running how else would this work?

Pretty 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.

[0] https://herdr.dev/

▲

andrewchambers 4 hours ago | parent | next [-]

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.

	▲	windexh8er 4 hours ago \| parent [-]
		But 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.

▲

krashidov 4 hours ago | parent | prev [-]

> Considering the harness needs to be running how else would this work?

you can just make new sessions for each new task?

	▲	sejje 2 hours ago \| parent [-]
		i tend to do this, or at least every so often. i just give it a config (agents.md etc) to where it knows what's going on, or can figure it out

▲

andrewchambers 4 hours ago | parent | prev [-]

Codex remote control serve can run continuously.

Sometimes 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.