fix(server): explain outdated Codex service tiers

[StiensWout]

Codex CLI 0.129 and older cannot read the default and priority service tier names written by newer Codex clients. T3 Code currently reports the resulting config reload failure without identifying the installed version or the required update.

Recognize that exact parser failure, probe codex --version, and publish the version with a clear requirement for Codex CLI 0.130.0 or newer. Publishing the version also lets the existing provider update flow offer its normal update action.

Fixes #8602

Tested with the focused provider registry suite, server lint, and server typecheck.

Built with GPT-5.6 Sol in the Codex harness inside T3 Code.

---

Note

Low Risk
Changes are limited to Codex provider status probing and user-facing error text on an existing failure path, with no auth or session behavior changes.

Overview
When the Codex app-server probe fails because the installed CLI cannot parse newer service tier values (default / priority in config), the server now recognizes that error pattern, runs codex --version, and surfaces the detected version on the provider status.

The probe error message is extended with guidance to upgrade to Codex CLI 0.130.0+ and refresh provider status, so users get a clear fix instead of a raw config reload failure. Publishing version on the error snapshot also keeps the normal provider update flow available.

checkCodexProviderStatus accepts an injectable versionProbe (defaulting to the new CLI probe) for tests; a registry test covers the legacy tier failure path with a mocked 0.129.0 version.

^{Reviewed by Cursor Bugbot for commit 20c7d2c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Add legacy Codex service tier detection and version probe to checkCodexProviderStatus

• Adds probeCodexCliVersion which runs codex --version and parses the output, returning null on failure.
• Adds isLegacyCodexServiceTierError to match known legacy service tier error patterns in CodexAppServerRequestError.
• On legacy service tier errors, checkCodexProviderStatus now probes the CLI version, populates the snapshot version field, and appends guidance recommending upgrade to 0.130.0 or newer.
• Adds a test in ProviderRegistry.test.ts covering the legacy error path with a simulated version of 0.129.0.

^{Macroscope summarized 20c7d2c.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b99df114-f0a4-4a9d-bfc4-8afae99f3ed8

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Approved at 20c7d2c

Macroscope's review found this PR approvable — This is a focused diagnostic fix confined to a specific Codex provider failure path, adding a bounded version probe and clearer upgrade guidance. Existing provider behavior and defaults remain unchanged, and the new branch has targeted test coverage.

^{You can add or adjust custom eligibility rules. Learn more.}

[MarkBekooy]

Thanks! This was indeed the case. My Codex desktop app was up-to-date, but the Codex CLI was not... Update available! 0.117.0 -> 0.139.0