Terminal pets do not work in Windows Terminal because image protocol is not detected

[ItsLasa]

What version of Codex CLI is running?

codex-cli 0.142.1

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.2-codex

What platform is your computer?

Windows 11 x64 -- (Output from PowerShell:) $([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })

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

Windows Terminal ,PowerShell

Codex doctor report

What issue are you seeing?

Pets aren’t available in this terminal. Terminal pets need image support, and this terminal environment doesn’t expose a supported image protocol.

What steps can reproduce the bug?

Install the latest Codex CLI.
Open Windows Terminal (PowerShell).
Launch Codex CLI.
Enable or trigger terminal pets.
Observe the warning:

What is the expected behavior?

No response

Additional information

Operating System: Windows 11 x64
Terminal: Windows Terminal + PowerShell
Feature affected: Terminal Pets
The issue appears related to image protocol detection (Kitty Graphics/Sixel).
It would be helpful if Codex could detect Windows Terminal separately and provide more specific guidance instead of the generic unsupported-terminal message.

[Nicolas0315]

I traced this to a narrow detector edge case and pushed a patch branch:

• Branch: Nicolas0315:codex/windows-terminal-wt-session
• Commit: e13fb7a35 fix(tui): honor WT_SESSION for terminal pets
• Compare: https://github.com/openai/codex/compare/main...Nicolas0315:codex:codex/windows-terminal-wt-session?expand=1

Current main already supports Windows Terminal as Sixel-capable once the terminal detector returns TerminalName::WindowsTerminal. The edge case is that TERM_PROGRAM is evaluated before WT_SESSION; if a shell/wrapper sets an unknown value like TERM_PROGRAM=PowerShell, that masks the later WT_SESSION probe and pets fall back to the generic unsupported-terminal warning.

The patch keeps recognized TERM_PROGRAM values working as-is, but lets WT_SESSION identify Windows Terminal when TERM_PROGRAM is present and unrecognized.

Verification:

• Windows local: just fmt
• Windows local: just test -p codex-terminal-detection detects_windows_terminal -> passed
• Windows local: just test -p codex-tui pet_image_support_detects_sixel_terminals -> passed
• Windows local: cargo check -p codex-terminal-detection
• Windows local: git diff --check
• SSH rtx4090: both focused tests passed via just test
• SSH cyberagent-mac-m5max: fresh origin/main checkout + patch, both focused tests passed via cargo test

I attempted to open a draft PR against openai/codex, but GitHub returned:

GraphQL: Nicolas0315 does not have the correct permissions to execute `CreatePullRequest` (createPullRequest)

Leaving the branch/compare here for maintainers.