Codex CLI 0.148.0-alpha.14

• [new] Thread queue support on the app server: add, list, update, reorder, start, and delete queued threads, with change notifications so clients can stay in sync.
• [new] Expanded configuration surface for plugins, computer-use requirements, analytics, and per-thread model defaults.
• [new] MCP-oriented config/types and hook handling, including clearer server identity and environment-variable matching.
• [changed] Model upgrade metadata carries more detail for surfacing upgrade information to clients.
• [changed] Filesystem path handling gains glob-pattern matching (via wildmatch).
• [changed] Login/account flows include Amazon Bedrock as a path alongside existing options.
• [changed] Client messaging events move from chunk-oriented payloads toward whole-message result events.
• [removed] The o1 model identifier is no longer advertised in the built-in model list.
• [removed] The dedicated JSONL exec event-processor path is gone as part of exec/output cleanup.

Under the hood

• New thread-queue request processor wires the queue operations end to end.
• Shared MCP types land in config to tighten how servers, env matchers, and related settings are represented.
• Dependency set picks up wildmatch for pattern matching used in path/glob handling.
• TUI chat-widget internals are trimmed (token chart palette and turn-runtime pieces removed or folded elsewhere).
• Several typed request/response payloads and error/info variants are reshaped around queueing, approvals, capabilities discovery, and remote-control flows.

Upgrade notes

• If you still select or pin o1 explicitly, switch to a supported model — it is no longer in the built-in list.
• Clients that consumed chunked client-message events should expect the newer whole-message result shape.
• Integrators using app-server APIs can adopt the thread-queue methods and ThreadQueueChanged notifications when ready; existing non-queue flows are otherwise unchanged.