On windows terminal when ssh to a linux host it render error

[andjohnsonj5]

What version of Codex is running?

v0.44.0

Which model were you using?

gpt-5-codex

What platform is your computer?

Linux 6.12.43+deb13-amd64 x86_64 unknown

What steps can reproduce the bug?

on windows terminal, ssh to a linux host, then execute codex

What is the expected behavior?

The rendering of the input box should be normal.

What do you see instead?

Additional information

it leaks some string

› 10;rgb:cccc/cccc/cccc11;rgb:0c0c/0c0c/0c0c

It's more likely to happen when the network is unstable.

[github-actions]

Potential duplicates detected:

• codex 0.44.0 breaks input on fish #4749
• Bug: input textarea background not rendering correctly in tmux session #4744

Powered by Codex Action

[andjohnsonj5]

I dug into this today and it looks like this report is separate from the tmux background/palette issues that were tracked in #4744/#4747.\n\nWhat is happening here: when we regain terminal focus we call , which emits the OSC 10/11 queries ( / ). Those responses come back over the same PTY and crossterm delivers each printable byte as a key event. Because the input stack treats them as real keystrokes, they get appended to the composer, so you see strings like .\n\nIn other words, this is not the background rendering bug fixed by #4747; it is that the OSC response stream bleeds into user input. We need to either filter OSC sequences out of the event loop (so they never reach handling) or change the default-color querying strategy so the replies are consumed out-of-band (e.g. via a raw read that does not race with the input loop).],

[andjohnsonj5]

@bolinfest

[andjohnsonj5]

@dylan-hurd-oai

[TaoSeekAI]

ubuntu 24
same issue

[superido245w]

The same problem occurs when trying to SSH to Ubuntu 24 using macOS Terminal, Tabby, or Visual Code. Because of the same color detection problem, Codex Resume has become unavailable and the history conversation list cannot be successfully displayed.

[vbmania]

The same issue occurs in macOS 0.45.0

[linQian99]

same here

[pixeldepartment]

same here

[claytongentry]

I notice when it leaks this string, oftentimes if I've been prompted to permit a command, the first result in the selection ("Yes") is automatically selected when I focus the terminal window, without me hitting Enter. This is significantly more problematic — even potentially dangerous — than the character leak itself. Raising because they seem to occur together.