[Bug]: Can't use Codex after updating to 0.0.23

[limwa]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

1. Start the app
2. Create a new thread, select any Codex model
3. Send a message

Expected behavior

No error should occurr

Actual behavior

There is an error, thread doesn't start

Impact

Blocks work completely

Version or commit

0.0.23

Environment

NixOS unstable; codex-cli 0.128.0

Logs or stack traces

ProviderAdapterProcessError: Provider adapter process error (codex) for thread d111c0b4-3308-4bba-b7d9-d548f95743d0: Invalid thread/start payload: Missing key
  at ["thread"]["sessionId"]
    at file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:47896:74
    at file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/node_modules/effect/dist/internal/effect.js:1309:96
    at ~effect/Utils/internal (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/node_modules/effect/dist/Utils.js:69:12)
    at startSession (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:58946:59)
    at startSession (definition) (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:25804:30)
    at ensureSessionForThread (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:59026:10)
    at ensureSessionForThread (definition) (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:58892:40)
    at processTurnStartRequested (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:59285:12)
    at processTurnStartRequested (definition) (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:59112:43)
    at processDomainEvent (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:59301:46)
    at processDomainEvent (definition) (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:59269:36) {
  [cause]: CodexAppServerRequestError: Invalid thread/start payload: Missing key
    at ["thread"]["sessionId"]
      at CodexAppServerRequestError.invalidParams (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:30334:10)
      at file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/apps/server/dist/bin.mjs:45593:108
      at file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/node_modules/effect/dist/internal/effect.js:1309:96
      at ~effect/Utils/internal (file:///nix/store/nl531xwsmcrqy4v2a1b77jnc2dzh76xq-t3code-nightly-0.0.24-nightly.20260511.260/libexec/t3code/node_modules/effect/dist/Utils.js:69:12)
}

Screenshots, recordings, or supporting files

Screenshot From 2026-05-11 22-00-16.png

Workaround

Rolling back the version to 0.0.23-nightly.20260507.219 works.

[limwa]

I still need to investigate if this happens with the AppImage version as well. The version I'm using is built from source using Nix (https://github.com/limwa/nix-t3code, same packaging as the one present in https://github.com/NixOS/nixpkgs)

[limwa]

Just checked and the bug also happens in the AppImage build. It also happens when running npx t3. I've updated the issue description to state that the issue is in apps/server.

[limwa]

Tracked the issue down to an outdated codex-cli. It would be great if T3 Code would let us know if the codex-cli version is incompatible with the T3 Code version we're running. Thank you!