top of page

Codex says the model "requires a newer version of Codex" even after updating: every cause and fix

4 hours ago
9 min read
Cover with the OpenAI logo and the title Codex says the model requires a newer version of Codex even after updating: every cause and fix. Data Studios original cover

Last verified: November 16, 2026


You pick a model in Codex, send a prompt, and instead of an answer you get a message telling you that the model requires a newer version of Codex and asking you to upgrade the app or the command-line tool. Many developers do exactly that, restart, and see the same message again. The reason is usually simple: the copy of Codex that sends your request is older than the one you updated, because the desktop app, the editor extension and the standalone command-line tool each carry their own Codex version, and OpenAI's own troubleshooting page says the app and the CLI can include different versions.


The message is not always about your installation. On November 10, 2026, users on Linux, macOS and Windows saw it in VS Code and in the CLI with up-to-date clients, and an OpenAI engineer confirmed on the Codex issue tracker the next day that the problem had been fixed on the server side. The same error also appeared in July 2026 when a previous model reached Codex, so it tends to return whenever a new model is added. The sections below show how to tell which case you are in, how to update the right component on each platform, and what is documented by OpenAI versus what users have only reported.


··········


⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣

THE CODEX "REQUIRES A NEWER VERSION" MESSAGE AND WHERE IT APPEARS.


The full text is the same in every Codex surface, with only the model name changing. In the reports of November 2026 the request came back as an HTTP 400 error of type invalid_request_error, which means the server refused the request before the model started working. Some users saw the model disappear from the model picker at the same time, with the picker briefly showing "Custom", and a remote context compaction failing with the same message.


........


Where you see it

What it looks like

What it usually points to

Codex desktop app

Error in the chat after sending a prompt

The app's own bundled Codex version

VS Code, Cursor or Windsurf extension

Error in the chat panel; model picker may show "Custom"

The CLI bundled with the extension

Codex CLI in a terminal

HTTP 400 invalid_request_error with the same text

The codex binary that your shell actually runs

Extension or CLI log

Warning about unknown model and fallback metadata

The local model catalog does not know the model


........


The exact strings people search for are these, copied from the reports on the Codex issue tracker and the OpenAI Developer Community:


The 'gpt-6.1-sol' model requires a newer version of Codex. Please upgrade to the latest app or CLI and try again.
Unknown model gpt-6.1-sol is used. This will use fallback model metadata.
Model metadata for `gpt-5.6-sol` not found. Defaulting to fallback metadata.

The second and third lines are warnings, written to the VS Code extension log and printed by the CLI, which say that your local copy of Codex has no description of the model in its catalog. A model catalog is the list of models, with their settings, that each Codex release ships with; OpenAI's changelog records when a model is added to it, for example GPT-6.1 Terra joining the bundled catalogs in Codex CLI 0.165.0 and 0.166.0 at the end of October 2026.


··········


WHY CODEX STILL SAYS "REQUIRES A NEWER VERSION" AFTER AN UPDATE: CAUSES TABLE.


........


Cause

How to check

Fix

You updated a different Codex component

Compare `codex --version` with the app or extension version; the troubleshooting page says they can differ

Update the component that shows the error

The editor extension uses its own bundled CLI

The extension log shows a bundled CLI version older than your terminal's

Update the extension; several users pointed it to a newer standalone CLI

An older codex binary runs first on your PATH

`where.exe codex` on Windows, `which -a codex` on macOS and Linux list more than one

Remove or update the extra copy so one install remains

Your package source lags behind the release

Homebrew reports "already installed" while npm offers a higher version

Install from npm or the standalone installer

An old Codex process is still running

Error persists in one window while a fresh terminal works

Quit Codex completely, including background processes, and reopen

Server-side model catalog problem

Error appears for many users at once on current versions

Wait for OpenAI's fix; use another model meanwhile

Open bug in one client

Same account works in the CLI but fails in the desktop app

Use the working client and follow the issue


........


The first two rows cover most single-user cases. The last two are outside your control, and no local change will clear them.


··········


HOW TO FIND WHICH CODEX COMPONENT IS OUT OF DATE.


OpenAI's troubleshooting page states that the ChatGPT desktop app and the Codex CLI can include different Codex versions, and that a feature may reach one surface before the other. It suggests running `codex --version` for the CLI and checking the version bundled with the desktop app separately. The editor extension adds a third copy: in the November reports, the VS Code extension version 26.1021.22027 was running a bundled Codex CLI 0.164.0 alpha build, while the reporters' terminals already had 0.167.1.


1. Note where the error appears: desktop app, editor panel or terminal. That surface is the one to update.


2. In a terminal, run `codex --version` and compare it with the latest release listed in the official changelog (Codex CLI 0.169.0, released on November 13, 2026, at the time of writing).


3. In your editor, open the extensions view and check whether the Codex extension has an update waiting. The extension's log is where the "Unknown model" warning appears, and the bundled CLI version is usually printed near it.


4. For the desktop app, OpenAI's troubleshooting advice for app problems starts with updating the app. After the update, quit it completely and open it again.


5. Send a short prompt with the same model from the CLI, for example with `codex --model <model name>`, which the official settings page uses as its example of choosing a model. If the CLI works and the app or extension does not, the problem is in that other component.


........


Version check

Command or place

Value seen in reports

Standalone CLI

`codex --version`

codex-cli 0.167.1 (still failing on Windows on Nov 10)

CLI bundled with the VS Code extension

Extension log

0.164.0 alpha build inside extension 26.1021.22027

Desktop app on Linux

App version

26.1103.60933 (failing while CLI 0.167.1 worked)

Latest CLI release

Official changelog

0.169.0, November 13, 2026


........


··········


STEP-BY-STEP FIXES FOR EACH CODEX INSTALL METHOD.


Standalone CLI installed with npm. The official CLI page gives `npm install -g @openai/codex` for both installing and updating, and the changelog lists a pinned command for every release. Run one of the following, then open a new terminal and check the version again.


npm install -g @openai/codex
npm install -g @openai/codex@0.169.0

Homebrew on macOS or Linux. The official update command is the cask command below. Two open reports on the Codex issue tracker describe Homebrew serving an older release than npm: one for macOS, one for Linux, where the reporter's Linuxbrew install stayed on 0.130.0 for days after 0.131.0 was published. A July 2026 report of this same error came from a Homebrew user whose terminal said the latest version was already installed. If Homebrew says you are up to date but the changelog lists a newer release, the official alternatives are npm or the standalone installer.


brew upgrade --cask codex

Standalone installer. The official page uses the same command to install and to update.


curl -fsSL https://chatgpt.com/codex/install.sh | sh
powershell -ExecutionPolicy ByPass -c "irm https://chatgpt.com/codex/install.ps1 | iex"

The first line is for macOS and Linux, the second for a new PowerShell window on Windows. Two reports on the issue tracker describe the built-in updater picking the standalone installer path when Codex was originally installed with npm, and not handling several install targets clearly. If you used more than one method over time, check which copy runs before and after updating.


More than one codex on the PATH. On Windows, `where.exe codex` lists every copy in the order the shell will try them; on macOS and Linux, `which -a codex` does the same. A user who answered the Windows report suggested exactly this check, together with comparing the local version with the one the server sees. Keep one install method and remove the others with the tool that installed them.


VS Code, Cursor and Windsurf extension. Update the extension first, reload the editor window, and try again. During the November incident, several users reported that installing the latest standalone CLI and setting the extension's `chatgpt.cliExecutable` setting to that binary's path, followed by a window reload, made the extension work. That setting is described in user reports on the Codex issue tracker and does not appear on the extension's settings page that OpenAI publishes, so treat it as a reported workaround and remove it once the extension catches up. One Windows user said the extension started working after a global npm upgrade, without any other change.


Desktop app. Update the app, then quit it fully, including any tray icon, and reopen it. On Linux, an open report from November 11, 2026 describes the desktop app rejecting the model on version 26.1103.60933 while the CLI on the same account worked; until a fix is listed, the CLI or the editor extension is the practical way to use that model on that system.


A process that survived the update. A commenter on the Windows report suggested that an older Codex app-server or background process can keep handling requests after an upgrade. Closing every Codex window, ending remaining processes and starting again costs a minute and rules this out.


··········


[[ADPLUS_300x250_1]]

WHAT OPENAI DOCUMENTS ABOUT CODEX VERSIONS AND WHAT USERS ONLY REPORT.


........


Statement

Status

Source type

Desktop app and CLI can include different Codex versions

Documented

OpenAI troubleshooting page

Install and update commands for npm, Homebrew and the installer

Documented

Official Codex CLI page

New models are added to the bundled catalogs in specific CLI releases

Documented

Official changelog (e.g. GPT-6.1 Terra in 0.165.0 and 0.166.0)

CLI 0.169.0 warns when a CLI model is absent from the ChatGPT model list

Documented

Official changelog, November 13, 2026

November 10 errors were fixed on the backend

Confirmed by an OpenAI engineer

Codex issue tracker, November 11, 2026

The extension runs a bundled CLI that can be older than yours

Reported by several users

Codex issue tracker

`chatgpt.cliExecutable` points the extension to a newer CLI

Reported by several users

Codex issue tracker

Homebrew lags behind npm

Reported, issues still open

Codex issue tracker

Linux desktop app fails while the CLI works

Reported, issue still open

Codex issue tracker


........


The November 10 episode shows why the message can mislead. Users reported that the model vanished from the refreshed catalog that Codex downloads while it was still present in the catalog bundled with their client, and every surface then showed the upgrade message. An OpenAI engineer replied the same day that the team was working on it and wrote on November 11 that the fix had been applied on the backend, after which users confirmed the model was back. Upgrading, reinstalling or changing settings would not have helped during those hours.


One open request on the tracker asks OpenAI to make the message name the outdated component, its detected version and the minimum compatible version, and to check compatibility when a model is selected instead of after a prompt is sent. None of that is in the product as of this check, so the version comparison above remains a manual step.


··········


⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁤

HOW TO AVOID THE CODEX UPGRADE ERROR AFTER THE NEXT MODEL LAUNCH.


New models reach the desktop app, the extension and the CLI through separate releases, and the changelog shows catalog changes in almost every CLI version of October and November 2026. When a new model is announced, update all three components on the same day, reload your editor and restart the app. Codex CLI 0.169.0 also adds a warning when the model set in the CLI is missing from your ChatGPT model list, which gives an earlier signal than a failed prompt.


If the error appears for a model that worked an hour earlier and nothing on your machine changed, look for other reports before reinstalling. A wave of identical reports on the Codex issue tracker, as on November 10, usually means a server-side problem. In the meantime, switch to another model with the `/model` command, and use `/` in the message composer to send feedback to the team, as the troubleshooting page suggests. Errors that look similar have different causes: a model that is temporarily overloaded produces a capacity message, covered in our guide to the "Selected model is at capacity" error, and dropped connections show up as Codex reconnecting and "stream disconnected before completion". Plan limits are a separate matter again, explained in our article on the shared Codex token usage limit.


··········


CODEX "REQUIRES A NEWER VERSION": WHAT FIXES IT AND WHAT DOES NOT.


The message is accurate in one narrow sense: the Codex client that sent the request did not recognize the model. In most cases that client is the desktop app or the CLI bundled inside the editor extension, and updating the standalone CLI in a terminal changes neither of them. Checking `codex --version`, the extension log and the app version side by side, then updating the component that shows the error, resolves the single-user cases reported in November 2026.


Two situations need no local fix at all. The November 10 errors ended when OpenAI corrected the model catalog on its servers, and the Linux desktop app report remains open with the CLI working on the same account. Homebrew users who are told they already have the latest release should compare it with the official changelog and switch to npm or the standalone installer when the numbers differ, because that lag has been reported more than once in 2026.


··········


FOLLOW US FOR MORE.


·····


DATA STUDIOS


·····


datastudios.org


bottom of page