Codex Diff missing background highlights on Remote-SSH

[WeiyiTian]

What version of the IDE extension are you using?

26.406.31014

What subscription do you have?

GPT Plus

Which IDE are you using?

VS Code

What platform is your computer?

Darwin 25.4.0 arm64 arm

What issue are you seeing?

In the Codex Diff view over an SSH connection, the red/green background highlights for changed lines are missing.

What steps can reproduce the bug?

1. Open VS Code and connect to a remote server using the Remote-SSH extension.
2. Open a project and modify any file.
3. Trigger a code edit using Codex, which opens the Codex Diff view for review.
4. Observe that the red (deleted) and green (added) line-level background highlights are completely transparent/missing.
5. Attempting to reload the window or change themes does not resolve the issue.

The specific code doesn't matter; all Codex-generated edits consistently fail to render the expected line-level background highlights.

What is the expected behavior?

The Codex Diff view should render full-width background highlights (red for deletions, green for additions).

Additional information

No response

[github-actions]

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

• Codex stuck on Dark Theme #15684
• v26.323.20928 regression: VS Code extension conversation panel becomes opaque black on macOS #15738
• VS Code extension spikes CPU and logs "open-in-target not supported in extension" while rendering diffs after Codex edits files #16850

Powered by Codex Action

[gcbartlett]

This is not just a Remote SSH thing; it happens to me in VSCode's Codex Chat summaries of (local) code changes, and in the Codex Diff (review) window. Seems to have been introduced in the 26.406.31014 release; the previous 26.325.31654 release is ok.

The line numbers are colored red/green, but the backgrounds are not colored at all:

[Ntropic]

Unreadable for colorblind people! with the background color at least it was somewhat ok! also allow a color blind mode, or just let people configure it themselves....

[ayasa520]

Looks like it's been fixed