›_ Codex Issues
Codex Issues / #7364

Codex stops react on typing. After few attempts to quit by ctrl+c shows error "failed 5: I/O error"

Resolved 💬 7 comments Opened Nov 28, 2025 by it-sha Closed Mar 29, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

v0.63.0

What subscription do you have?

Pro

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

Microsoft Windows NT 10.0.22631.0 x64

What issue are you seeing?

During long-running codex (Codex CLI) sessions inside WSL, interactive input gradually becomes sluggish and then stops responding. Pressing Ctrl+C only takes effect after 5–6 attempts, after which the terminal starts printing read failed 5: I/O error repeatedly.

What steps can reproduce the bug?

  1. Start codex inside WSL with VSCode bash and keep working for a prolonged period (around 5-7 minutes).
  2. Observe growing input latency. See moment when work becomes impossible
  3. Try to quit by Ctrl+C. See error "failed 5: I/O error"

What is the expected behavior?

I can see typed text with same speed as at the beginning
I can continue work with Codex

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 7 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #6576

Powered by Codex Action

it-sha · 7 months ago

Additional info:
To notify I am using:

// config.toml
notify = ["bash", "-lc", "powershell.exe -c \"[System.Media.SystemSounds]::Hand.Play()\""]

May it be related?
If so, what should I do to get a notification without this issue?

etraut-openai contributor · 7 months ago

We haven't hard reports of sluggish behavior in WSL from other users, so we will need to determine what is different about your system or configuration.

You mentioned that you're using a notify script. Do you suspect that's related to the problem? Have you tried disabling it to see if that fixes it?

Are you using any other non-default configuration options?

it-sha · 7 months ago

@etraut-openai I double checked
If remove notify = ["bash", "-lc", "powershell.exe -c \"[System.Media.SystemSounds]::Hand.Play()\""] the Codex works without this issue

But could you recommend a reliable way to get notifications that could work on WSL without this problem?
Codex works quite slowly, so it's very important for development experience

tzzht · 7 months ago

Title: Encountering the same issue with Codex CLI on WSL

Comment:

Hi, I'm encountering the same issue with Codex CLI on my system. I have the same configuration as described in the issue #7364, and the issue persists with the "read failed 5: I/O error" after running Codex CLI in my WSL environment. The CLI becomes unresponsive after a period of usage, and I also experience delays when trying to interrupt the process using Ctrl+C.

Additionally, I have a notify setup that calls a Python script to trigger a system notification in Windows. The notification is successfully triggered, but Codex input response becomes very slow or unresponsive when this happens. This suggests that the issue may be related to Codex’s interaction with WSL and external processes like notifications.

My Setup:

  • Operating System: Windows 11 26100.7462 with WSL 2
  • Codex CLI Version: v0.77.0
  • Steps to Reproduce:
  1. Run Codex CLI in WSL
  2. Use Codex for a while and try to interact with it.
  3. After some time, the CLI stops responding.
  4. Codex typing window: "write failed 32: Broken pipe"
  5. Ctrl+C results in "read failed 5: I/O error".
  6. I have notify set up to trigger a Windows notification via a Python script. The notification is triggered, but input response in Codex becomes very slow or completely unresponsive.

The issue seems to be related to WSL's handling of I/O operations and Codex CLI’s performance when interacting with external processes like notifications. Could the team please look into this and provide a fix for better compatibility with Windows + WSL environments, especially when using external notifications?

Thank you for your time and attention to this issue!

jainabhishek · 6 months ago

I am experiencing this on mac

etraut-openai contributor · 3 months ago

This bug report hasn't received any upvotes or additional posts in three months. Closing.