openai / openai/codex

Codex CLI intermittently panics during tasks on Windows with RUST_BACKTRACE message

Open
#41,952 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug CLI windows-os
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What version of Codex CLI is running?

codex-cli 0.151.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.6 sol high/medium

What platform is your computer?

Windows x86_64

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

PowerShell

Codex doctor report

What issue are you seeing?
Description

Codex CLI intermittently crashes while executing tasks on Windows. This has happened multiple times during normal task execution.

Immediately before the process terminates, the terminal displays:

note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

### What steps can reproduce the bug?

The issue is intermittent, but the general sequence is:
1. Start Codex CLI from PowerShell.
2. Ask Codex to execute a task involving multiple file or shell operations.
3. Allow the task to run for some time.
4. Codex CLI unexpectedly panics and terminates.
5. The terminal prints the RUST_BACKTRACE=1 message.
I have not yet identified a single command that reliably triggers the panic.

### What is the expected behavior?

Codex CLI should either complete the task or report a recoverable command/tool error without terminating the entire session.

**Actual behavior**
The Codex CLI process panics and exits, interrupting the active task.

### Additional information

The problem has occurred multiple times rather than as a one-time failure. Please let me know if a full backtrace, diagnostic report, session log, or additional environment information would be helpful.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start Codex CLI from PowerShell on Windows and exercise the described multi-file or shell-operation workflow. Collect a full RUST_BACKTRACE, diagnostic report, or session log when the intermittent panic occurs; done means the task completes or reports a recoverable command/tool error without terminating the session.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, rust
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.