Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Bug: Backspace stops working after concurrent subprocesses on Windows

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…

Code Example

codex doctor --json completed successfully.

  Overall status: ok
  Codex version: 0.134.0
  Notable details:

  - Auth configured with ChatGPT tokens and OPENAI_API_KEY present
  - Network and WebSocket reachability both ok
  - Installation is npm-managed on Windows x86_64
  - No MCP servers configured
  - Current version matches latest cached version: 0.134.0
RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

0.134.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.5 default

What platform is your computer?

Windows 10

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

Windows command

Codex doctor report

codex doctor --json completed successfully.

  Overall status: ok
  Codex version: 0.134.0
  Notable details:

  - Auth configured with ChatGPT tokens and OPENAI_API_KEY present
  - Network and WebSocket reachability both ok
  - Installation is npm-managed on Windows x86_64
  - No MCP servers configured
  - Current version matches latest cached version: 0.134.0

What issue are you seeing?

In codex installed on windows, certain commands corrupts the prompt. Backspace adds characters in stead of deleting them.

What steps can reproduce the bug?

Grant full permissions, and provide this exact prompt (this reproduces it almost always):

Run this command: powershell powershell -NoProfile -Command "$p1 = Start-Process wsl -ArgumentList '-- echo ONE' -PassThru -NoNewWindow; $p2 = Start-Process wsl -ArgumentList '-- echo TWO' -PassThru -NoNewWindow; Wait-Process -Id $p1.Id,$p2.Id

What is the expected behavior?

Backspace should work properly after codex completes a prompt.

Additional information

No response

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

codex - 💡(How to fix) Fix Bug: Backspace stops working after concurrent subprocesses on Windows