Codex CLI monitor

Open 💬 2 comments Opened Aug 11, 2026 by Andromeda1957
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What variant of Codex are you using?

CLI

What feature would you like to see?

ThreadID 019fefdd-9144-7bb2-a889-960945ad2527

Codex needs a feature that is available in the claude code CLI harness if you want claude to monitor a process it will just set a monitor and do it, And when the process exits or the condition the monitor was monitoring is met, claude automatically starts doing what it was told to do. However codex doesnt really have this built into the harness, yes what I am doing here is a workaround using a /goal , but full monitor functionality would be much cleaner. Also I trust gpt 5.6 sol alot more than claude for being able to monitor a process and acting when the condition of the monitor when I am AFK.

Additional information

_No response_

View original on GitHub ↗

2 Comments

github-actions[bot] contributor · 17 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #37238
  • #36668

Powered by Codex Action

jdcodes1 · 9 days ago

The pieces for a first-class monitor mostly exist in the runtime already, which makes this more tractable than a from-scratch harness feature:

  • Background processes survive turns via unified-exec sessions, and the model can already poll them (functions.wait / code-mode exec_command+wait — modulo the completion-reporting bug in #38093).
  • The wake-when-idle primitive exists too: mailbox items flagged trigger_turn start a synthetic same-session turn when the thread is idle (core/src/tasks/mod.rs, maybe_start_turn_for_pending_work) — it's how inter-agent messages and goal continuations resume work without a user prompt (#38221 asks to expose the same primitive to Stop hooks).

What's missing is only the connector: a monitor tool that registers "when process X exits / output matches Y", parks without burning a goal-loop turn, and enqueues a trigger-turn mailbox item when the condition fires. That's meaningfully cheaper than the /goal workaround, which relaunches a full model turn every idle cycle to re-check (and is why it consumes usage while you're AFK — see #38524/#38437).