DEV Community

aicoding-guide
aicoding-guide

Posted on Originally published at aicoding-guide.com

Codex CLI v0.166 adds codex queue --resume and codex doctor --network-only

#codex #codexcli #updates #codexdoctor

Originally published at https://aicoding-guide.com.

Codex CLI v0.166.0 ships six features and seven fixes. Two matter day to day: codex queue --resume and codex doctor --network-only.

Both are flags on existing commands, so knowing what each command already does is the quickest way to see what changed.

Key point
What this article covers

  • How codex queue works and the situation --resume fixes
  • What codex doctor checks, and what --network-only narrows it to
  • Approval settings and token accounting now surviving resume and fork

codex queue --resume resumes the thread

The release notes read: "Added codex queue --resume to resume unloaded threads after queueing a message."

codex queue itself is documented: it queues a text message for an existing session.

codex queue --thread <SESSION_ID> --message "Run the remaining checks"
Enter fullscreen mode Exit fullscreen mode
Option Detail
--thread A UUID or an exact session name; use a UUID when sessions share a name
--message The text to queue
Others --remote and --remote-auth-token-env are accepted; image attachments are not

Previously, queueing a message to a thread that was not loaded left it waiting. With --resume, queueing and resuming happen in one step — useful when a script or CI job adds work to an existing session.

--resume is not in the commands documentation
As of 2026-11-02, the flags documented for codex queue are --thread, --message, --remote and --remote-auth-token-env. There is no entry for --resume; it appears only in the release notes.

codex doctor --network-only narrows the report

The other addition: "Added codex doctor --network-only for focused configuration, connectivity, and WebSocket diagnostics."

codex doctor is the diagnostic command to run before filing a support issue or while investigating a broken installation. The documentation describes its scope as "installation, configuration, authentication, runtime, Git, terminal, app-server, and thread inventory health".

# The full report
codex doctor

# Narrowed to configuration, connectivity and WebSocket
codex doctor --network-only
Enter fullscreen mode Exit fullscreen mode

The full report includes the thread inventory, so it takes a while. When the symptom is clearly network-side — connections failing behind a proxy, WebSockets dropping — --network-only is the faster path.

This flag could not be confirmed in the documentation either: codex doctor's option table is rendered dynamically on that page, so individual flags are not readable from the Markdown.

For the network proxy settings themselves, see Combining approval_policy and sandbox_mode in Codex.

Transcript handling and the other features

The remaining four are display and interaction changes.

Addition What it does
Transcript selection Keyboard-driven, with word, line and page motions, integrated search, and configurable shortcuts
Markdown rendering Made consistent in async questions, choices, answers and transcript replies
GPT-6.1 Terra Added to the bundled, Vertex AI and Amazon Bedrock model catalogs
Safety-block explanations Clearer reasons in the TUI, with selectable safer follow-up prompts

GPT-6.1 Terra reached the bundled catalog in v0.165.0; v0.166.0 adds it to the Vertex AI and Amazon Bedrock catalogs. That follows v0.165.0 making Vertex AI a built-in provider via model_provider = "gcp" — see Codex CLI v0.165 makes Vertex AI a built-in provider.

Fixes around resume and fork

Two of the seven fixes concern resuming and forking sessions.

  • Approval and permission settings persist: "Preserved acknowledged approval and permission settings when resuming or forking threads."
  • Reasoning-token accounting persists: "Preserved reasoning-token accounting across resume and fork to avoid premature compaction."

The second has the clearer practical effect. When the accounting reset, a resumed session could be judged to have met the compaction threshold while it actually had room left, so context was lost earlier than it needed to be.

Also fixed: spawned descendant threads are restored when their parent is unarchived, app-server thread startup and shutdown races are resolved with completed runtimes released promptly, and TUI reconnection recovery now handles offline /quit and /exit.

Summary

  • codex queue --resume queues a message and resumes an unloaded thread in one step
  • codex queue takes a UUID or exact session name in --thread and does not support image attachments
  • codex doctor --network-only narrows diagnostics to configuration, connectivity and WebSocket
  • Approval settings and reasoning-token accounting now survive resume and fork
  • Neither --resume nor --network-only could be confirmed in the official commands documentation

Top comments (0)