Last month I wrote about how I kept Claude Code running forever with tmux, launchctl, and a resume prompt. That setup was ugly, but the model was simple: keep a session alive, or bring it back and tell it exactly how to continue.
Trying Codex automations made me realize the comparison is a bit subtler than I first thought.
The good part
The value still isn’t “automation” in the vague productivity-tool sense. It’s heartbeat. Some work should wake up every few minutes, look around, react, and go back to sleep. Monitoring Slack is one example. Reviewing PRs. Watching deploys. Orchestration, really.
That’s also why OpenClaw’s heartbeat became such a big deal. People don’t just want one-shot prompts anymore. They want agents that can keep an eye on things and wake themselves up when needed.
And Codex does make that easier. The app already has the scheduler. The Mac app can stay open on login. A pinned thread can wake up on cadence and keep working in the same conversation.
That makes using Codex Scheduler much easier.
What it actually is
Thread automations are described as recurring wake-up calls attached to a thread. That’s important. They preserve thread context, but they still wake up and run the same prompt again. In other words, this feels more like scheduled re-entry into the same thread than one continuously running local agent.
That may sound like a small distinction, but it changes how I think about it. My old Claude setup was clunky, but it was explicit. I knew where the restart logic lived. I knew when the session died. I knew what prompt brought it back. And most importantly, I knew the memories were local to Claude’s project.
Codex memories are more global, thus that might be mix in more context than necessary during the automation loop.
The pitfall
I also hit a dumb bug getting this to work. One thread refused to create the automation, citing no such scheduler tool. Then a new chat worked immediately.
Digging their sqlite, it seems the thread has the feature only during creation.
And you don’t need to pin the thread.