›_ Codex Issues
Codex Issues / #23474

Codex CLI streams unexpected characters when ran via ssh in PowerShell

Resolved 💬 4 comments Opened May 19, 2026 by sgiardl Closed Jun 9, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

codex --version 0.131.0

What subscription do you have?

Pro

Which model were you using?

_No response_

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

PowerShell 7.6.1

Codex doctor report

What issue are you seeing?

I am running Codex CLI via ssh in PowerShell, after installing 0.131.0, I am seeing this stream of unexpected characters in PowerShell, it used to work perfectly in 0.130.0. Note that when I do "codex resume" the output is fine, but when I start a conversation or load up an existing conversation, this is what I'm seeing:

<img width="1734" height="927" alt="Image" src="https://github.com/user-attachments/assets/3cf5dc63-f1fe-42c5-8f90-d65ebacd64ed" />

Note that running this on the local machine works with no problem, but when accessing via ssh I am seeing this issue.

What steps can reproduce the bug?

  1. Connect via ssh in PowerShell 7.6.1 to a remote machine
  2. cd to the directory I want to work in
  3. run "codex resume"
  4. select the conversation
  5. hit enter
  6. I am seeing this stream of unexpected characters

What is the expected behavior?

Codex conversation launches as usual, just like in 0.130.0

Additional information

_No response_

View original on GitHub ↗

4 Comments

github-actions[bot] contributor · 3 months ago

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

  • #23374
  • #23031

Powered by Codex Action

sgiardl · 3 months ago

It does seem to be a duplicate of #23374 but mine has more detailed steps.

Key facts are:

  1. This only occurs when running it via ssh on another Windows machine
  2. This only occurs after starting a new session or restarting an existing session, does not occur when inside the "codex resume" part where you see previous sessions
kevod1997 · 3 months ago

I'm experiencing the exact same issue using PowerShell. As a temporary workaround, downgrading to 0.131.0-alpha.9 fixes the TUI rendering problem for now.

Has anyone found a way or a specific flag to make it work on the latest 0.131.0 without having to downgrade?"

hookland1-hub · 3 months ago
I'm experiencing the exact same issue using PowerShell. As a temporary workaround, downgrading to 0.131.0-alpha.9 fixes the TUI rendering problem for now. Has anyone found a way or a specific flag to make it work on the latest 0.131.0 without having to downgrade?"

I can confirm same situation here on the last official update. Had to downgrade to the 0.131.0-alpha.9 as suggested from @kevod1997 as current workaround