Feature Request: Create Codex Task from ChatGPT Conversation or Project

Resolved 💬 2 comments Opened Apr 27, 2026 by bigbobro Closed Jul 1, 2026

What variant of Codex are you using?

App

What feature would you like to see?

Problem:
ChatGPT is often where product thinking, requirement clarification, meeting analysis, and implementation planning happen. Codex is where execution happens. Today, moving from ChatGPT to Codex requires manual summarization and copy/paste.

Why Codex chat is not enough:
Codex already has a project chat, but that chat does not automatically have access to the broader ChatGPT-side context.

In real workflows, important background may come from:

  • multiple ChatGPT conversations
  • meeting recordings and summaries
  • uploaded documents
  • product discussions inside ChatGPT Projects
  • decisions, constraints, and open questions accumulated before coding starts

By the time users move to Codex, the key context often already exists in ChatGPT, not inside Codex. Manual copy/paste is workable, but inefficient. It also risks losing important decisions, constraints, and background information.

Suggested Solution:
Add a “Send to Codex” or “Create Codex Task” action from ChatGPT conversations and ChatGPT Projects.

The action should generate a structured task context for Codex, including:

  • background
  • final decisions
  • constraints
  • implementation scope
  • acceptance criteria
  • open questions
  • linked source conversations or project materials

Product Direction:
ChatGPT Project should be able to serve as an upstream context source for Codex workspace.

Expected Value:
This would reduce manual copy/paste, preserve decision history, avoid context loss, and make the transition from thinking to implementation much smoother.

Additional information

_No response_

View original on GitHub ↗

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