Headed screenshot capture on Windows is not deterministic enough for bounded UI proof passes on my display setup.

What version of Codex CLI is running?

codex-cli 0.121.0

What subscription do you have?

Chat GPT Pro

Which model were you using?

gpt-5.4 xhigh

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

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

Windows Terminal PowerShell

What issue are you seeing?

I am running on a 3840x2160 display, but the captured Discord proof images appear to use an inconsistent / effectively smaller frame, and the proof crops are not reliably centered on the actual message area I need. In practice this caused repeated recovery attempts, multiple fresh /omni_panel rerenders, overlapping-window residue, and a failed bounded proof run.

What steps can reproduce the bug?

Uploaded thread: 019dabad-292e-7633-b63e-57e7a35a9a8f

In the latest Channel Routing rerun, the pass itself recorded that:

• the proof exceeded the requested bound because multiple fresh /omni_panel success rows were generated during capture recovery
• the Discord window-handle capture path was not deterministic enough to avoid repeated rerenders and overlapping-window residue

Where-Object { $_.ProcessName -eq 'Discord' -and $_.MainWindowTitle -eq '_Channel Name_ | _Guild Name_
│ - Discord' } | Select-Object -First 1 Id,ProcessName,MainWindowTitle,MainWindowHandle | ConvertTo-Json
│ -Compress

Note: _Channel Name_ | _Guild Name_ were changed in this example and are available upon request

What is the expected behavior?

What would help:

• deterministic native-resolution window-handle capture on Windows
• configurable crop anchoring, especially lower-left message-area cropping for Discord UI proofs
• a clearer way to guarantee “capture exactly this visible message surface” without forcing repeated operator recovery steps

Additional information

This is separate from the earlier audit-framing issue. This feedback is about screenshot / proof-capture reliability only.