Codex Desktop: make “Report a bug / Send feedback” easy to discover

Open
#36,889 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust
Domain
desktop

Research direction

No files or tests are identified. Start by locating the Codex Desktop Help/Settings navigation and the existing slash-command feedback flow; done means a visible reporting entry is available without a slash command, with the proposed submission and privacy-review behavior defined across desktop platforms.

Written by the indexing model from the issue text.

Description

app enhancement
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:

  1. Expose Help → Report a bug / Send feedback.
  2. Pre-fill the Codex app version, OS, and display/environment details.
  3. Let the user attach a screenshot and optionally include the current session/logs, with an explicit privacy warning and preview.
  4. Return a feedback/session ID after submission.
  5. Optionally allow Codex to prepare and submit the report after explicit user approval (related: #26534).
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__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.

User feedback: Attach screenshots/files to Share feedback
  • Source: https://x.com/AndysTMC/status/2095203251943797188
  • Type: external
  • User reports (Ubuntu):
    • Requests image/file attachments in the ChatGPT desktop “Share feedback” form.
    • “Screenshots would make some issues much easier to explain.”
    • Asks: “Or am I missing an existing way to do this?”
Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.