Codex CLI Adds codex queue --resume to Wake Unloaded Threads After Queueing a Message

CodexOct 29, 2026View original changelog

Codex CLI 0.166.0 added a --resume option to the codex queue command. After a message is queued, the flag resumes a thread that is not currently loaded, so the queued message does not sit with an idle thread. A thread that is already loaded is left running.

Key Takeaways

codex queue --resume queues a message and then resumes the target thread when that thread is unloaded.
The flag is optional, so it is an addition to codex queue rather than a change to how the command works by default.
A thread that is already loaded is left running, so the flag does not interrupt active work.
The resume step works through the local daemon or a selected --remote server, according to the pull request.
If resumption fails, the command emits a warning but keeps the successful queue result, so the queued message is not lost.
It shipped in Codex CLI 0.166.0 (2026-10-29), alongside keyboard-driven transcript selection and codex doctor --network-only.

What Changed

Codex CLI 0.166.0 added an optional --resume flag to codex queue. The release note describes it in one line: "Added codex queue --resume to resume unloaded threads after queueing a message." The release's changelog list describes the underlying change as "Add optional thread resumption to codex queue."

How the Flag Works

codex queue is the command that queues a message for a Codex thread. With --resume, Codex goes one step further after the message is queued: if the target thread is unloaded, it resumes that thread. The pull request behind the change adds that the resume step works through the local daemon or a selected --remote server. A thread that is already loaded is left running, so the flag does not interrupt work that is already in progress.

The pull request also describes how failures are handled. If resuming the thread fails, the command prints a warning but keeps the successful queue result. The message stays queued either way.

When It Helps

The flag is aimed at workflows where a message is sent to a thread that may not be loaded at that moment. Instead of queueing the message and then separately resuming the thread, a developer or script can do both in a single codex queue --resume call. Because the flag is optional, existing codex queue usage is not described as changing.

Scope

The release note and the pull request give little more detail than the above. They do not define "unloaded" beyond the contrast with an already-loaded thread, and they do not state what happens without the flag. Developers can run codex queue --help on 0.166.0 for the full option text.