Skip to content

fix(codex): grace fallback for thread/resume failure on Codex 0.142+#276

Open
u-ichi wants to merge 1 commit into
fujibee:mainfrom
u-ichi:fix/codex-0142-thread-resume-fallback
Open

fix(codex): grace fallback for thread/resume failure on Codex 0.142+#276
u-ichi wants to merge 1 commit into
fujibee:mainfrom
u-ichi:fix/codex-0142-thread-resume-fallback

Conversation

@u-ichi

@u-ichi u-ichi commented Jul 1, 2026

Copy link
Copy Markdown

Summary

Codex CLI 0.142+ introduced --remote sessions where the rollout is not created,
causing thread/resume requests to fail. Without this fix, codex-bridge.js
calls die() on such failure and exits.

This PR wraps the thread/resume call in a try/catch and falls back to
threadIdle=true, turnActive=false when the resume fails, allowing turn/start
which only needs threadId to proceed. The bridge continues to operate in idle
state instead of exiting.

Related

Follow-up to #237 (fix(codex): keep Codex working across 0.142 upgrades).

Test plan

  • node --check scripts/drivers/types/codex/codex-bridge.js
  • npm test

🤖 Generated with Claude Code

Codex 0.142+ --remote sessions may not create a rollout, causing
thread/resume requests to fail. turn/start only needs threadId, so keep
the bridge alive by falling back to the idle state when resume fails.

Follow-up to 2f94765 (fix(codex): keep Codex working across 0.142 upgrades).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant