codex - 💡(How to fix) Fix CLI fails to start with Error: thread/start failed during TUI bootstrap [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18251Fetched 2026-04-17 08:30:50
View on GitHub
Comments
2
Participants
3
Timeline
9
Reactions
0
Timeline (top)
labeled ×5commented ×2unlabeled ×2

Error Message

After updating to 0.119.0 or later, codex always emits error: Error: thread/start failed during TUI bootstrap. Note that "Update available!" message is shown and then choose skip, the above error is emitted and exit. If using latest version, just fails to start with error.

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.119.0 or later

What subscription do you have?

Plus

Which model were you using?

CLI doesn't start

What platform is your computer?

WSL on Windows

What terminal emulator and version are you using (if applicable)?

Windows Terminal

What issue are you seeing?

After updating to 0.119.0 or later, codex always emits error: Error: thread/start failed during TUI bootstrap.

What steps can reproduce the bug?

Just run codex.

Note that "Update available!" message is shown and then choose skip, the above error is emitted and exit. If using latest version, just fails to start with error.

What is the expected behavior?

No response

Additional information

I have installed both Codex App and CLI.

extent analysis

TL;DR

The issue might be resolved by investigating compatibility issues between Codex CLI version 0.119.0 or later and the WSL on Windows environment.

Guidance

  • Verify that the error persists when running the CLI with the --no-tui flag to isolate the issue to the TUI bootstrap process.
  • Check the official Codex documentation for any known issues or compatibility notes related to running the CLI on WSL.
  • Consider uninstalling and reinstalling the Codex CLI to ensure a clean setup.
  • If the issue is specific to the WSL environment, try running the Codex CLI on a native Windows terminal or another environment to isolate the problem.

Notes

The issue may be specific to the combination of Codex CLI version 0.119.0 or later and the WSL on Windows environment, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Try running the CLI with the --no-tui flag or on a different environment to mitigate the issue, as the root cause is unclear and no clear fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING