OpenAI · 2026-08-20 · major
Codex CLI 0.149.0 — a dashboard for every running agent task
Codex CLI 0.149.0 adds an interactive `codex agents` dashboard for searching, starting, opening, renaming and stopping tasks. The same build adds `codex queue`, which sends a message into an existing local or remote session.
Codex CLI 0.149.0 puts every agent task behind one searchable dashboard you can drive with shortcuts.
Key specs
| GitHub stars | 111.1k |
|---|
Quick facts
| Maker | OpenAI |
|---|---|
| Version | 0.149.0 |
| Released | August 20, 2026 |
| License | Apache-2.0 |
| Written in | Rust |
| New commands | codex agents, codex queue, /cd, /pwd, /cwd |
| Requires | Node.js 16 or higher |
What is it?
An interactive `codex agents` dashboard is the headline change in Codex CLI 0.149.0. It searches, starts, opens, renames and stops tasks from one screen, with configurable shortcuts. A second new command, `codex queue`, sends a message into a session that is already running, local or remote. Codex CLI itself is OpenAI's terminal coding agent, written in Rust and shared under Apache-2.0.
How does it work?
Working-directory control moves inside the terminal UI: `/cd`, `/pwd` and `/cwd` set and report where a session runs, so you no longer restart Codex CLI to change folders. Vim editing picks up character replacement and more change motions such as `cw`, `c$` and `cc`. The `codex doctor` check now diagnoses endpoint protection, network and proxy failures, desktop app state, and update connectivity.
Why does it matter?
Running several coding agents at once used to mean guessing which terminal held which task. The dashboard and the queue command give that fleet a single front door. A quieter fix matters just as much for safety: resumed and forked threads now restore the permission profile they were started with, instead of silently falling back to whatever the current defaults happen to be. SDK users also gain exact CLI config overrides and can pick `max` or `ultra` reasoning effort.
Who is it for?
developers running several Codex tasks in parallel
Frequently asked questions
- Is Codex CLI open source?
- Yes. Codex CLI is published under the Apache-2.0 license on GitHub at openai/codex, where it has 111,133 stars. The agent is written in Rust and described by OpenAI as a lightweight coding agent that runs in your terminal. The npm package @openai/codex ships the same 0.149.0 build and needs Node.js 16 or higher.
- Can I send pull requests to the Codex repository?
- OpenAI would rather you did not open one cold. The 0.149.0 documentation update clarifies that external contributions to Codex should go through issues and design discussion rather than pull requests. The same docs pass also writes up DNS exfiltration risks and the trust limits of secure devcontainers, so start a conversation in an issue first.
- What did Codex CLI 0.149.0 fix for sub-agents?
- Codex CLI 0.149.0 removes duplicate sub-agent activity from the display and tightens terminal-UI routing for sub-agent notifications and approvals, so a prompt lands where you can answer it. Realtime WebRTC sideband connections also reconnect after an unexpected transport loss without dropping output that was still pending.
- Are there Windows-specific improvements in this Codex release?
- Yes. In Codex CLI 0.149.0, inline terminal-UI history stays available in Windows Terminal scrollback, so earlier turns do not vanish when you scroll back. The release also bounds replay buffers for inactive threads, which stops Codex from holding on to large amounts of streamed output you are no longer looking at.
- What happens to messages queued while a Codex session is idle?
- Queued messages now wake idle Codex sessions reliably in 0.149.0, rather than sitting until you touch the session yourself. The same fix resolves duplicate session names more usefully and preserves the semantics of pasted or deferred commands, so a message you queued behaves the same way it would have if you had typed it live.
Try it
npm install -g @openai/codex@0.149.0