openai / openai/codex

Send to Codex

Open
#46,311 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

CLI enhancement session
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

CLI & Web

What feature would you like to see?

Feature request: Attach an existing ChatGPT conversation to a Codex CLI session

I frequently use ChatGPT and Codex for two different parts of the same software-development workflow:

ChatGPT: research, web search, architecture, comparing libraries, discussing product decisions and requirements.

Codex CLI: reading the actual repository, implementing changes, running tests and debugging.

Today these two contexts are isolated. I have to manually copy conclusions from ChatGPT into Codex and then manually summarize Codex's implementation results back into ChatGPT.

I would like an explicit two-way handoff:

ChatGPT → Codex: attach a selected ChatGPT conversation to a Codex session so Codex can use its decisions and research as context.

Codex → ChatGPT: expose a compact summary of implementation state, changed files, test results and important discoveries back to the attached ChatGPT conversation.

This should be explicit and permission-based, rather than automatically sharing all conversations or repositories.

Example workflow:

ChatGPT research → architecture decision → Attach to Codex → implementation/tests → results returned to ChatGPT → further research/decision → Codex continues

This would make ChatGPT and Codex feel like two specialized interfaces to the same development workflow instead of two disconnected assistants.

The user should be the bridge between research and implementation conceptually, not a clipboard between two OpenAI products.

Additional information

No response

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.

Research direction

No files, tests, or entry points are named. Start by tracing how a Codex CLI session receives context and how an explicit, permission-based handoff could select a ChatGPT conversation. Done would include sending research context to Codex and returning implementation state, changed files, test results, and discoveries to ChatGPT.

Written by the indexing model from the issue text.

Assessment

Domain
ai, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.