Issue Station
Sign In
Tools hereToolbox

codex - 💡(How to fix) Fix Feature request: native ChatGPT<->Codex bridge and a visible feedback path [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18303•Fetched 2026-04-18 05:56:28
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
EARTHTOEDWARDEARTHTOEDWARD
Participants
EARTHTOEDWARDEARTHTOEDWARDetraut-openaietraut-openai
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1
RAW_BUFFERClick to expand / collapse

Opened from the Codex CLI feedback flow.

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

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

Two related product requests:

  1. There still seems to be no native way to promote an ordinary ChatGPT conversation into a Codex thread with a durable link back to the originating chat.
  2. The feedback path for ChatGPT/Codex product requests is still too invisible, especially compared with the clearer feedback/reporting affordances around Codex CLI / VS Code workflows.

1. Native ChatGPT <-> Codex bridge

Codex and ChatGPT are connected at the account level, but there is still no obvious first-party handoff from a normal ChatGPT discussion into Codex work.

What is blocking a native ChatGPT<->Codex bridge / plugin here?

I am not asking for raw transcript mirroring. A better design would likely be:

  • explicit handoff capsules
  • selected context / goals / constraints / artifacts
  • start or link a Codex thread from that object
  • query status / summaries / outputs later from the same durable object

2. More visible feedback process

Please make feedback submission much more visible inside ChatGPT and Codex.

Ideally there should be:

  • an obvious in-product route for feature requests, bugs, and workflow gaps
  • routing to the relevant team without users guessing which surface to use
  • a visible acknowledgement or case/reference ID
  • a clearer signal that feedback is being collected and reviewed systematically

A major reason engaged users feel ignored is not necessarily that feedback is never read, but that there is no obvious, durable in-product path for product feedback, especially in ordinary ChatGPT usage. Even if the feedback is being collected internally, the product currently does not communicate that well.

Main asks:

  • What is blocking a native ChatGPT<->Codex bridge?
  • Is that on the roadmap?
  • Can OpenAI create a more visible and trackable feedback process for ChatGPT/Codex product requests?

extent analysis

TL;DR

Implementing a native ChatGPT-Codex bridge and enhancing the feedback submission process can improve user experience and engagement.

Guidance

  • To create a native ChatGPT-Codex bridge, consider designing explicit handoff capsules that capture selected context, goals, constraints, and artifacts from ChatGPT discussions, allowing users to start or link a Codex thread from a durable object.
  • Enhance the feedback submission process by introducing an obvious in-product route for feature requests, bugs, and workflow gaps, ensuring routing to the relevant team and providing a visible acknowledgement or case/reference ID.
  • Develop a systematic approach to collecting and reviewing feedback, and communicate this process clearly to users to increase transparency and trust.
  • Consider implementing a query system for users to check the status, summaries, or outputs of their feedback submissions.

Example

No specific code snippet can be provided without more technical details, but a potential design for the handoff capsule could involve creating a JSON object that captures the necessary context and information from the ChatGPT discussion.

Notes

The implementation of these features may require significant development and design efforts, and it is essential to prioritize user needs and feedback to ensure that the solutions meet their expectations.

Recommendation

Apply workaround: Implementing a more visible and trackable feedback process for ChatGPT/Codex product requests can be a crucial step in improving user engagement and satisfaction, even if a native ChatGPT-Codex bridge is not immediately available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#task chaining#parallel task#integration issue#index setup#retrieval issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING