Codex CLI 0.167.0 shipped on 6 November 2026. It adds an agentAI agentAn AI program that performs work steps by itself, for example reading a message, drafting a reply, and recording the result.Open the glossary command center that can run without a daemon. The release also adds backend switching that keeps drafts, Google Cloud Vertex AI setup, and fixes for network approval prompts.
The upgrade is safe for most users, because the release notes do not list security fixes. Check 3 user-reported issues first, especially if you use codex exec with a goal or continue sessions from another device.
The agent command center is a terminal screen that shows your Codex sessions and lets you switch between them. You open it with codex agents. The daemon is the local Codex background server that shares sessions with more than 1 client, for example a terminal, the desktop app, and a phone.
What changed in Codex CLI 0.167.0?
Codex CLI 0.167.0 has 6 new features and 6 bug fixes, according to the openai/codex release notes on GitHub. The official Codex changelog shows the same date, 6 November 2026.
| Change | How to use it | Best for |
|---|---|---|
| Agent command center without a daemon | codex agents --no-daemon | Servers or containers with no daemon |
| Unread result markers | Automatic in the command center and the session picker | Users with many parallel sessions |
| Backend switching that keeps drafts | Session picker in the terminal | Users with more than 1 Codex server |
| Google Cloud Vertex AI setup | Enable the gcp_setup_wizard feature, then select "Sign in another way" | Teams with a Google Cloud account |
| macOS and Windows system proxy | Option in /experimental | Office networks with a proxy |
| Patch details during an approval prompt | Expand the patch details in the transcript | Users who review changes before they approve |
These bug fixes have the largest effect on daily use:
- Saved chats stay visible after you change the model provider. If a chat cannot resume, you can read its transcript and prepare a prompt for a new chat.
Ctrl+Lclears the screen, but you can still open earlier messages withCtrl+T.- Network approval prompts close when their requests end. Concurrent requests to the same endpoint prompt 1 at a time.
- Automatic compaction now counts output from failed responses and from responses with no token data.
For MCPMCPA standard that lets an AI program use your tools and data under clear permissions.Open the glossary users, 2 pull requests are worth a note. MCP approval metadata now includes tool names and annotation hints (PR #58161), and shared MCP connections now have per-chat leases (PR #57978). The release notes do not explain the user impact, so we do not draw more conclusions.
What is it like to use the agent command center?
The command center helps when you run more than 1 Codex session and lose track of which session is complete. Release 0.167.0 marks unread results and sorts tasks newest-first in each status group (PR #58714).
This change matches user feedback. On 30 October 2026, 1 user asked for the newest sessions at the top (issue #58373). On 4 November 2026, another user said that a long history needs many "Show more" clicks (issue #59396).
Some gaps remain. A dev container user reported that the command center shows folder names but not host names (issue #59947, 6 November 2026). When 2 machines have the same path, it is hard to tell the sessions apart.

Example scenario
This example is an illustration, not a testimonial. A small agency runs 3 Codex sessions on 1 VPS: session 1 fixes a landing pageLanding pageThe page an ad points to. It carries 1 offer and 1 action, with no menu pulling the visitor elsewhere.What is a landing page?, session 2 writes a tracking script, and session 3 checks an SEOSEOThe work of making your page easy to find and easy to choose in search results, without paying for ads.SEO services audit.
The developer opens codex agents --no-daemon through SSH. Completed sessions show an unread marker, so the developer reviews the results without 3 open terminals.
What did we test on 9 November 2026?
We ran Codex CLI 0.167.0 on 1 Linux machine with npx -y @openai/codex@0.167.0. This method does not replace the existing 0.160.0 installation on the same machine.
- In 0.160.0,
codex agents --helpsays "Browse all agent sessions on the shared local app-server daemon". The--no-daemonoption is not available. - In 0.167.0,
codex agents --helpsays "Open the agent command center to browse and switch sessions". The--no-daemonoption runs the overview with an embedded app server. - In 0.167.0,
codex features listshowsgcp_setup_wizardas stable with the value false. You must enable it yourself. codex app-server daemonhas the subcommandsversion,restart, andupdate. The help text forupdatesays that it "may interrupt running work".
We did not test sign-in, model calls, Vertex AI, or the proxy option. The results above only check the available commands and options.
Which issues do users still report?
On 9 November 2026, we found 3 user reports that can change an upgrade decision. Version 0.167.0 is still the latest stable release, and 0.168.0 and 0.169.0 are only alpha releases.
| Issue | Symptom | Version | Status on 9 November 2026 |
|---|---|---|---|
| #60308 | codex exec exits after the first turn and stops the automatic continuation of a goal | 0.159.0, 0.164.0, 0.167.0 | Open |
| #60310 | Android remote refuses a live task when the CLI and daemon versions are different | CLI 0.166.0, daemon 0.167.0 | Open |
| #60183 | codex resume --remote to a thread that is already running keeps the TUI busy, and Esc and Ctrl+C do not work normally | 0.167.0 | Closed on 8 November 2026, no new stable release yet |
Issue #60308 is not a new regression, because the reporter also reproduced it on 0.159.0 and 0.164.0. If your automation uses a goal in codex exec, check the task status after each run.
Issue #60310 gives a practical lesson: keep the CLI and the daemon on the same version. The command codex app-server daemon version shows both versions in JSON.

How do you upgrade to Codex CLI 0.167.0 safely?
Use the 6 steps below, and let running agent work complete first.
- Check the CLI version with
codex --version. - Check the daemon version with
codex app-server daemon version. - Try 0.167.0 without a change to the existing installation:
npx -y @openai/codex@0.167.0 agents --help. - Install 0.167.0 with your original install method. For npm, use
npm install -g @openai/codex@0.167.0. - Wait until all sessions are complete, then run
codex app-server daemon updateif the daemon version is still different. - Run
codex doctor --network-onlyto check the config, the network, and the WebSocket connection.
For Vertex AI, enable the feature with --enable gcp_setup_wizard or -c features.gcp_setup_wizard=true. Then select "Sign in another way" and use Application Default Credentials or a credential file.
Who should upgrade now?
Upgrade now if you run many parallel sessions, use servers with no daemon, or need Vertex AI. Wait if your automation depends on codex resume --remote to threads that are already running.
- Developers with many agent sessions: upgrade, then use the command center to track results.
- Teams on Google Cloud: upgrade, then enable
gcp_setup_wizard. - Users on office networks with a proxy: upgrade, then try the system proxy option in
/experimentalon macOS or Windows. - Business owners and marketers: this release is for the terminal CLI. The desktop app and ChatGPT have their own version numbers.
If your team uses more than 1 agent, also read our Claude Code 2.1.319 upgrade notes and the Dots and Codex automation update.
Conclusion: what to do this week
Install Codex CLI 0.167.0 if you manage more than 1 agent session at a time. After the upgrade, keep the CLI and the daemon on the same version, then test codex agents --no-daemon on 1 machine first.
If your team needs a safe and measurable agent workflow, see our agentic AI training or ask Rama Digital for an AI workflow audit.
Questions and answers
Does Codex CLI 0.167.0 fix security vulnerabilities?
The 0.167.0 release notes do not list a CVE or a security fix. You can wait for a break in your work, unless you need the new features.
What is the difference between codex agents and codex agents --no-daemon?
The codex agents command uses the shared local daemon. The --no-daemon option runs the overview with an embedded app server, so it works on machines with no daemon.
Is the Vertex AI setup active after the upgrade?
No. In our test, the gcp_setup_wizard feature had the value false by default. Enable the feature, then select "Sign in another way" when you sign in.
Do old chats disappear when I change the model provider?
Not in 0.167.0. Saved chats stay visible after you change the model provider, and you can still read a chat that cannot resume as a transcript.
Why does the phone remote refuse a running task?
Issue #60310 reports this symptom when CLI 0.166.0 and daemon 0.167.0 have different versions. The cause is not confirmed, so keep both versions the same and check them with codex app-server daemon version.

