Repository navigation
[Bug]: Codex cant update #8051
Description
Activity
I can't use t3 code with codex not being able to update inside t3 code.
ProviderAdapterProcessError: Provider adapter process error (codex) for thread 3d53a50d-475e-4cf2-a694-d043069e6cae: Codex App Server process exited with code 1
at file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:159222:67
at file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/Schema-DyMTXMnS.mjs:9178:96
at ~effect/Utils/internal (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/Schema-DyMTXMnS.mjs:2430:10)
at startSession (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178166:59)
at startSession (definition) (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:100151:23)
at ensureSessionForThread (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178247:10)
at ensureSessionForThread (definition) (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178089:33)
at processTurnStartRequested (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178654:12)
at processTurnStartRequested (definition) (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178438:36)
at processDomainEvent (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178670:46)
at processDomainEvent (definition) (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:178635:29) {
[cause]: CodexAppServerProcessExitedError: Codex App Server process exited with code 1
at Object.onSuccess (file:///C:/Users/Admin/AppData/Local/Programs/t3code/resources/server.asar/apps/server/dist/bin.mjs:156311:23)
}I'm experiencing the same. I was on Nightly build when the error arose. I switched to Stable and the error remained. Switched back to Nightly and updates have not resolved it.
Codex fixed it for me, resolution steps below.
Root cause: T3 Code resolves
codexto%APPDATA%\npm\codex.cmdon Windows. In my case, that npm installation was missing its
optional Windows binary package (@openai/codex-win32-x64), socodex app-serverexited with code 1 during the provider probe.The native Codex install was working. Reinstalling the npm package with optional dependencies fixed the probe.
Manual fix:
-
Close and reopen T3 Code after the repair.
-
In PowerShell, reinstall Codex with optional dependencies:
npm install -g @openai/codex@0.149.1 --include=optional
Or use
@latestif you are intentionally updating Codex. -
Confirm the npm launcher works:
& "$env:APPDATA\npm\codex.cmd" --version
-
In T3 Code, go to Settings → Providers → Codex and refresh the provider status.
If the npm launcher still causes issues, set the Codex provider's Binary path to the native executable instead:
C:\Users<username>\AppData\Local\Programs\OpenAI\Codex\bin\codex.exe
Reacted by TheDarkSkyXD-
I'm experiencing these issues as well.
My solution is to run
codex updateinside my terminal.It updates Codex for me, but the Provider update by T3Code doesn't work for me.
@t3dotgg Can you please fix this. Thanks
Reacted by Ben Aylesyup, having the same problem here
@t3dotgg
Current pain point: (Linux install)bash # Requires sudo npm install -g --allow-scripts=@openai/codex @openai/codex@latest # Doesn't require sudo codex update Proposed solution:A simple toggle or detection mechanism that determines whether Codex was installed via npm or as a standalone CLI tool. This would allow codex update to:
- Use the appropriate update method based on installation source
- Avoid permission issues by not falling back to npm global installs when the user originally used the direct CLI installer
This seems like a lightweight fix that would significantly improve the update experience for npm-based installations.
also, because t3code uses npm to install the updates, if you use something like mise (which is the default way on Omarchy) it breaks
Same here. If installed with the curl shell script then you need to use
codex updateI just submitted a PR that will fix this :)
Reacted by Vytor Rennan, Bob Mwangi and TheDarkSkyXDThe conventional Linux mise npm-backend case is fixed on main by #9927, merged September 5 as c7dc3cbd. T3 no longer offers npm updates inside mise's tool-version directory; these installations stay manual-only. Ordinary npm globals and globals under mise-managed Node retain npm updates.
This does not add automatic mise updates, which remain a separate proposal in #9225. Custom
MISE_DATA_DIRroots with a different basename, native-wrapper detection, and the original Windows optional-binary failure are outside this fix. Native Windows/macOS updates were not tested or run. Keeping this issue open for those remaining cases.GPT 6 Astra via Codex in T3 Code.
A further mise-shim case from #10050 is fixed on main by #10085, merged September 5 as 2271a27d. A shim resolving to Homebrew's mise executable now stays manual-only instead of offering
brew upgrade miseand comparing Codex against mise's version. Automatic mise updates remain a separate proposal in #9225.This does not resolve the original Windows optional-binary failure, native-wrapper detection or every custom installation layout. Verification used actual CodexDriver and Linux filesystem/PATH fixtures with synthetic Homebrew metadata, not native macOS/Windows updates. The separate stderr-display concern is unchanged. This issue remains open.
GPT 6 Astra via Codex in T3 Code
Before submitting
Area
apps/desktop
Steps to reproduce
trying to update the codex provider
Expected behavior
the provider to update form t3 code
Actual behavior
update teh provider
Impact
Blocks work completely
Version or commit
0.0.33
Environment
windows
Logs or stack traces
Screenshots, recordings, or supporting files
T3_Code_(Alpha)_WriRDUXIg1.png
Workaround
No response