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

[it-sha]

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

[github-actions[bot]]

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

• #6576

Powered by Codex Action

[it-sha]

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]

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]

@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