Problem：Codex App display wrong

Welcome to the forum!

You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex.

I had ChatGPT look for the closest related issue and it identified:

github.com/openai/codex

Codex desktop on macOS shows blurred white overlay at certain window widths

opened 12:06AM - 24 Apr 26 UTC

      stonezzz
    

bug app

What version of the Codex App are you using (From “About Codex” dialog)? 26….422.21459 (2049) ### What subscription do you have? plus ### What platform is your computer? macOS：15.7.5 (24G624) ### What issue are you seeing? Issue: When the app window width crosses a certain threshold, a layout/rendering bug appears. Window height does not affect the issue. Symptoms: - In the Plugins and Skills pages, part of the UI gets covered by a blurred white overlay. - In the chat window, similar blurred white regions can appear near the lower area. - Clicking the affected area can still open the underlying popup/popover content correctly. - After closing or returning, the blurred overlay remains visible. - If I narrow the window below a certain width, the issue disappears. - If I widen the window again past that width, the issue returns. Expected behavior: Popovers, sheets, or overlays should render normally without leaving a blurred white layer covering page content. Actual behavior: A blurred white overlay appears at specific window widths, as if the overlay background is rendered but the content layer is misplaced, clipped, or hidden. Notes: - This is reproducible on the built-in display. - The issue is width-dependent, not height-dependent. - Changing macOS display scaling does not prevent it. ### What steps can reproduce the bug? + ### What is the expected behavior? No response ### Additional information No response

One useful aspect of that issue is that etraut-openai, an OpenAI developer, is tracking this issue as the primary and closing others as duplicates of it.

If that issue matches your problem, consider adding a reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.

If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.