Feature request: make feedback submission more visible and trackable in ChatGPT/Codex

Resolved 💬 2 comments Opened Apr 17, 2026 by EARTHTOEDWARD Closed May 31, 2026

Opened as a separate request after openai/codex#18303 was closed with guidance to split feature requests.

Uploaded Codex CLI feedback thread ID: 019d9a46-fe44-7491-91dc-7690b2298431

Related public discussion: https://community.openai.com/t/feature-request-native-chatgpt-codex-thread-bridge/1379162

Problem:

For users who invest heavily in ChatGPT and Codex, the feedback path still feels too invisible and too non-durable, especially in ordinary ChatGPT usage.

Codex CLI / VS Code workflows give a clearer sense that feedback can be submitted somewhere. ChatGPT does not. Even when feedback is likely being collected internally, the product does not make that clear enough.

Requested improvement:

  • an obvious in-product feedback entry point in ChatGPT and Codex
  • a way to classify feedback as bug / feature request / workflow gap
  • routing to the relevant team without users guessing which surface to use
  • a visible acknowledgement or case/reference ID after submission
  • clearer confirmation that product feedback is being collected and reviewed systematically

This is broader than #17251, which is about a confirmation screen after /feedback. The request here is for a more discoverable and trustworthy feedback path across ChatGPT/Codex surfaces, not only a post-submit confirmation in the Codex app.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗