CLI freezing since 117 on WSL

Open 💬 5 comments Opened Apr 11, 2026 by DeanStr
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

120

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

WSL

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

Bash

What issue are you seeing?

Since 117 the CLI sometimes freezes eg I will see Waiting for background terminal (5m 10s • esc to interrupt) but the time doesnt increase and it never changes however it is still running because if I give it time and close it and then resume the session the task has completed (if i gave it enough time, if not it says it was interrupted).

This started in 117, it was there in 118. I reverted to 116 with no issue. Tried updating to 120 today and its still happening.

What steps can reproduce the bug?

Use Codex CLI 117+ in WSL, observe relatively frequent freezes like this.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 4 months ago

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

  • #16779
  • #16311
  • #17433
  • #16904

Powered by Codex Action

etraut-openai contributor · 4 months ago

If you're able to repro, please use /feedback to upload logs and session details, then post the thread ID here.

DeanStr · 4 months ago
If you're able to repro, please use /feedback to upload logs and session details, then post the thread ID here.

019d7f49-9d2c-7ba0-a20b-92d8396a7c03

DeanStr · 4 months ago

Two more to add to above:
019d7fb5-04c3-7bf3-bc5a-69c3a28b9653
019d7f9f-a7af-7880-9dd6-373778e8af3c

DeanStr · 4 months ago

Another issue I beleive is related, and follows the same pattern of starting in 117 and is still there (though maybe less common in 120 than it was in 117/118):

Final messages from the agent are cut off and I have to ask it to repeat its message to get the full display.

I have a session here 019d80d8-33df-7011-a092-a15a3da3a357