You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a persistent, clearly visible Report a bug / Send feedback entry to Codex Desktop, ideally under the Help menu and/or Settings.
The current feedback path is difficult to discover. The official troubleshooting documentation says to type / in the message composer to access feedback, but users who are trying to report an app-level UI bug do not naturally look for a slash command inside a coding conversation. There is no comparably prominent reporting entry in the normal desktop navigation.
A good flow could:
Expose Help → Report a bug / Send feedback.
Pre-fill the Codex app version, OS, and display/environment details.
Let the user attach a screenshot and optionally include the current session/logs, with an explicit privacy warning and preview.
A user encountered a long-standing Windows multi-monitor rendering bug (#25826) but could not find the reporting entry. Their comparison was that Claude Desktop makes bug reporting much more visible. When the reporting affordance is hidden behind a composer command, useful product feedback is likely to be abandoned.
Expected behavior
A user who notices an app-level bug should be able to find the reporting action in a few seconds without knowing a slash command or searching external documentation.
Environment
Observed in Codex Desktop for Windows, Microsoft Store/MSIX package:
OpenAI.Codex_26.727.6591.0_x64__2p2nqsd0c76g0
This request is about discoverability across desktop platforms, not only this version.
Disclosure: this issue was prepared and posted by Codex at the account owner's request.
What feature would you like to see?
Add a persistent, clearly visible Report a bug / Send feedback entry to Codex Desktop, ideally under the Help menu and/or Settings.
The current feedback path is difficult to discover. The official troubleshooting documentation says to type
/in the message composer to access feedback, but users who are trying to report an app-level UI bug do not naturally look for a slash command inside a coding conversation. There is no comparably prominent reporting entry in the normal desktop navigation.A good flow could:
Why this matters
A user encountered a long-standing Windows multi-monitor rendering bug (#25826) but could not find the reporting entry. Their comparison was that Claude Desktop makes bug reporting much more visible. When the reporting affordance is hidden behind a composer command, useful product feedback is likely to be abandoned.
Expected behavior
A user who notices an app-level bug should be able to find the reporting action in a few seconds without knowing a slash command or searching external documentation.
Environment
Observed in Codex Desktop for Windows, Microsoft Store/MSIX package:
OpenAI.Codex_26.727.6591.0_x64__2p2nqsd0c76g0This request is about discoverability across desktop platforms, not only this version.
Disclosure: this issue was prepared and posted by Codex at the account owner's request.