Title
Add thumbs up / thumbs down feedback at the end of each Codex conversation
Summary
I would like Codex to include a lightweight feedback mechanism at the end of each conversation, using two simple controls: a thumbs up and a thumbs down. This would give users an immediate way to indicate whether a response was helpful, relevant, and aligned with their intent.
Problem
At the moment, there is no fast, structured way for users to signal whether a Codex response met their needs. When feedback is difficult or missing, useful signals about response quality, relevance, and user satisfaction can be lost. This makes it harder to identify weak spots, measure improvement over time, and understand where the product is performing well or poorly across different types of tasks.
Proposed Feature
Add a feedback prompt at the end of each Codex conversation or response flow with:
-
a thumbs up option for helpful or satisfactory responses
-
a thumbs down option for unhelpful, inaccurate, or incomplete responses
This should be lightweight, unobtrusive, and fast to use. The initial version can remain intentionally simple, with the option to expand later into more detailed feedback collection when needed.
Why This Would Help
A simple feedback control would create a direct signal from real users at the moment of interaction. That signal could help the team:
-
monitor response quality more consistently
-
identify patterns in user satisfaction across prompts, workflows, or topics
-
surface areas where Codex is underperforming
-
prioritise product and model improvements using real usage feedback
-
build a foundation for optional follow-up feedback in future versions
Expected Benefits
This feature would improve the product in several ways:
First, it would support continuous improvement by creating a steady stream of user-quality signals. Second, it would give the team more actionable insight into how users experience Codex in practice, not only how it performs in testing. Third, it would allow performance trends to be observed over time, including whether changes are improving the user experience. Finally, it would establish a simple feedback layer that could later support richer options such as short reason codes or optional written comments.
Suggested Design Principles
The feature would be strongest if it is:
-
visible but not disruptive
-
available immediately after a response or conversation ends
-
easy to use in one click
-
optional, with no interruption to workflow
-
extensible for future detailed feedback flows
Conclusion
A thumbs up / thumbs down feedback control is a small product addition with high practical value. It would give Codex a simple and scalable way to capture user sentiment, strengthen quality monitoring, and support ongoing refinement based on real interaction data. This would help improve both the usefulness of responses and the overall user experience.