6.2.0 — Codex cells say when they are waiting for your approval

A snapshot as of 6.2.0 (released 2026-09-25). It will go stale as the app moves on — that is expected, and the living reference is the guide each section links to.

Nothing to configure. There is one prompt to answer, once, the first time you open a Codex cell.

A Codex approval prompt reads as “Needs input”

Until now a Codex cell stayed on working for as long as Codex sat on its own approval prompt (“Would you like to run the following command?”). It could wait there for hours, and nothing told you.

Now that prompt marks the cell Needs input, exactly as a Claude permission prompt does. It raises the attention mark on a cell you are not looking at, plays the sound, and sends the Waiting for you push if phone notifications are on. Answering the prompt and finishing the turn moves it on as usual.

The one thing to do. The first Codex cell you open after upgrading shows this in the terminal:

  Hooks need review
  1 hook is new or changed.
  Hooks can run outside the sandbox after you trust them.
› 1. Review hooks
  2. Trust all and continue
  3. Continue without trusting (hooks won't run)

That hook is MulmoTerminal’s. Pick 2. Trust all and continue, or 1 to read it first. It only posts the approval prompt’s details to MulmoTerminal on this machine. Codex remembers the answer in ~/.codex/config.toml, and the hook is identical for every cell, so later cells, other projects and other ports do not ask again. Pick 3 and the cell behaves as it did in 6.1.0.

How to tell it worked. Open a Codex cell, ask it to do something that needs approval (for example, writing a file outside the project), and click away to another cell. When the prompt appears, the Codex cell turns to Needs input.

What it does not cover.

• A Codex session that MulmoTerminal starts with a prompt already typed in — a collection action or a background chat — gets no hook, because the one-time question above would swallow that prompt. Those sessions still sit on an approval prompt without a sound.
• Windows: no hook is registered there yet.
• Measured against Codex CLI 0.156.1.

More on what each agent reports: Which coding agent. Which moments reach the phone: Mobile notifications.

Fixed: status behind an http_proxy

If MulmoTerminal was started with http_proxy or ALL_PROXY set (and NO_PROXY did not cover localhost), Claude’s hooks sent their reports to the proxy instead of to MulmoTerminal. The result was that a Claude cell never showed working or done, and the prompt text went to the proxy. The rate-limit reading, Copilot’s hook and the curl commands in MulmoTerminal’s own skills had the same problem. All of them now go straight to MulmoTerminal, whatever proxy is set.

How to tell you have the fix. Nothing to configure. With a proxy variable set, a Claude cell’s dot moves again when you send it a prompt.