Codex 0.149.0

When juggling multiple AI tasks, you no longer have to switch blindly across terminal windows.

Run codex agents in your terminal to open an interactive dashboard. Inside this view, you can search, start, open, rename, and stop tasks. The interface also provides configurable shortcuts so you can navigate and manage all your background jobs using your preferred keystrokes.

When talking with Codex in the terminal, you no longer need to exit and restart just to switch folders. Inside a TUI (text-based user interface) session, you can now enter /cd to change your working directory, or run /pwd and /cwd to print your current location. This allows you to navigate across different project folders within the same conversation without losing your ongoing thread.

When you need to send instructions from another window to an existing task, codex queue offers a direct channel.

This new command delivers messages to existing local or remote sessions. Queued messages now reliably wake idle sessions, resolve duplicate session names more intelligently, and preserve the original semantics of pasted or deferred commands without corruption.

For developers accustomed to Vim bindings in the terminal, editing prompts is now much smoother. Codex has expanded Vim editing with single-character replacement and additional change motions. You can now use cw to change a word, c$ to change to the end of the line, or cc to rewrite the entire current line. These key combinations let you reshape text in place without backspacing character by character.

When troubleshooting connection hiccups or frozen environments, the built-in diagnostic tool can pinpoint issues faster.

Running codex doctor now inspects four critical areas: endpoint protection software interference, network and proxy failures, desktop application state, and update server connectivity. When something breaks, you can immediately tell whether corporate security software or network routing is at fault.

Developers calling Codex through an SDK (Software Development Kit) now enjoy much tighter control over execution. You can directly pass exact CLI configuration overrides from your code to fine-tune settings for specific tasks. In addition, when tackling complex logic that requires deep deliberation, you can set the reasoning effort to max or ultra to dedicate maximum reasoning capacity to the problem.

When receiving output over real-time channels, brief network hiccups will no longer cause missing data.

Realtime WebRTC sideband connections now automatically reconnect after an unexpected transport loss. Once reconnected, pending output generated during the interruption is preserved and delivered rather than dropped, ensuring you never miss streamed responses.

For developers running Codex inside Windows Terminal, reviewing past discussions is now completely effortless. Previously in inline TUI mode, conversation output was not properly retained in the terminal's native scrollback buffer. Inline TUI history now remains available in Windows Terminal scrollback, allowing you to scroll up anytime to inspect previous code snippets and explanations.

When keeping multiple background tasks open, Codex will no longer consume excessive memory by hoarding old streamed text.

Replay buffers for inactive TUI threads are now strictly bounded. This restriction prevents inactive sessions from retaining massive amounts of streamed output in memory, reducing system resource usage and keeping long-running sessions lightweight and stable.

For developers looking to contribute to Codex, the contribution guidelines are now clearer. The documentation clarifies that external contributions should begin with an issue and architectural design discussion rather than jumping straight to a pull request. Aligning on the design before writing code helps avoid wasted effort.

When running untrusted code inside secure containers, developers now have clearer guidance on potential security boundaries. The documentation now details the trust limitations of secure devcontainers (isolated containerized development environments). It specifically highlights DNS exfiltration risks, explaining how malicious code could leak sensitive data via domain lookup requests. This guidance reminds teams to audit outbound network policies even within containerized setups.