Uh oh!
There was an error while loading. Please reload this page.
fix(server): soften Codex CLI version enforcement - #609
Conversation
T3 Code 0.0.5 regressed enterprise and internal Codex builds by hard blocking session startup whenever codex-cli 0.111.0 reported a parsable version below the open-source minimum, even if the CLI still worked. Remove the synchronous startup gate and keep the minimum-version check as a provider-health warning instead, so users still see compatibility feedback without losing access to working internal Codex forks. Closespingdotgg#604
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
binbandit
commented
Mar 10, 2026
@juliusmarminge this one is an easy fix for orgs who roll their own codex -- will help a lot of people |
Noojuno
commented
Mar 10, 2026
@binbandit If we're moving it to a warning, I think we should move the version to 0.99.0 to help with #736. The |
Da1sypetals
commented
Mar 12, 2026
Want this feature very bad 😢 thanks! |
Da1sypetals
commented
Mar 13, 2026
😢 Anyone on this |
binbandit
commented
Mar 13, 2026
Dont worry, i'm still on this. Just got lots of other PR's to be across too |
…heck-warning # Conflicts: # apps/server/src/provider/Layers/ProviderHealth.test.ts
Da1sypetals
commented
Mar 20, 2026
Plz also do this for claude code, we also use a enterprise encapsulation of claude-code Appreciate your work! ❤️ ❤️ |
binbandit
commented
Mar 20, 2026
Reach out on discord, let me see exactly what you guys are doing so i can better tailor this.
|
Summary
codex --versionstartup gate added in 0.0.5 that blocks sessions for any parsable Codex version below0.37.0.Closes#604
Why
Issue #604 reports a real regression from
0.0.4->0.0.5: internal/company Codex builds can report a different version number than the open-source CLI, and0.0.5started hard-failing session startup before even attemptingcodex app-server.I validated the regression in the code:
assertSupportedCodexCliVersion()preflight inapps/server/src/codexAppServerManager.tscodex --versionand throws before startup when the parsed version is< 0.37.0status: "error"/available: falseThat is too strict for enterprise forks where version numbers diverge but runtime compatibility can still be fine.
Changes
apps/server/src/codexAppServerManager.tscodex app-serverbe the source of truth for whether the provider can actually startapps/server/src/provider/Layers/ProviderHealth.tswarningwhen auth is otherwise healthyValidation
Passed:
bun lintbun typecheckbun run test src/codexAppServerManager.test.tsinapps/serverbun run test src/provider/Layers/ProviderHealth.test.tsinapps/serverRepo baseline issue still present:
bun run teststill fails on pre-existing unrelated web storage test regressions inapps/web/src/terminalStateStore.test.tsandapps/web/src/composerDraftStore.test.tsNote
Downgrade Codex CLI version enforcement from error to warning in provider health checks
CodexAppServerManager.startSession, so an unsupported CLI version no longer causesstartFailedbefore the process spawns.checkCodexProviderStatusin ProviderHealth.ts to returnstatus: 'warning'(available: true) instead ofstatus: 'error'(available: false) when the CLI is below the minimum supported version.'warning'instead of'error'.Macroscope summarized 82c37ad.