light theme: Codex preview and live session render dark background incorrectly

[Sogl]

Summary

In agent-deck light theme, codex sessions render incorrectly:

• the preview pane shows dark/black background bars
• the live attached Codex session still shows a dark/black input background

This does not match how Codex looks when run directly in a light terminal.

Environment

• Agent Deck: v0.25.1
• Codex: v0.114.0
• Terminal: Ghostty
• light theme
• macOS Soquoia 15.7.4 (24G517)

Expected

In light theme, Codex should render similarly to direct Ghostty + codex:

• no dark/black bars in preview
• no dark/black input background in the live session

Actual

• preview shows dark background blocks
• live attached session shows a dark/black input line background

Important observation

Running codex directly in Ghostty looks correct.

So the issue seems specific to how agent-deck handles Codex in light theme, especially around preview rendering and interactive session display.

Notes

I was able to locally improve the preview behavior with a Codex-assisted patch, but the live session still renders incorrectly in light theme.

Screenshots

Codex in Ghostty - OK:

Codex in agent-deck (2 panels mode) - black input background:

Codex in agent-deck (session mode) - black input background:

[asheshgoplani]

Fixed in v1.3 milestone. Code committed on main branch.

[Sogl]

@asheshgoplani I checked main and don't see the COLORFGBG-related changes there yet; is there another commit/PR that closed this?

[Sogl]

@asheshgoplani I tested v0.26.0

Current result:

1. Preview pane is improved:

   • the dark background bleed is gone
   • but it still does not match native Ghostty + codex rendering, because the soft light-gray input background is not preserved
   

2. Live attached Codex session is still broken:

   • the black input background is still present in the main interactive session view
   • so the core live-session symptom from this issue is still reproducible
   

Important detail:
I can see COLORFGBG='0;15' being exported in the launch command now, so this part is in place, but it is not sufficient to fix the live interactive rendering issue.

I think the issue should be reopened.