[Feature Request] Bring Codex-context-aware Quick Chat and “Add to Task” workflow to mobile Remote
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What feature would you like to see?
Please bring the Codex Desktop context-aware Quick Chat / More Details → Add to Task workflow to the ChatGPT mobile Codex Remote experience.
Current desktop workflow
On Codex Desktop, a user can:
- Open an existing Codex task/session.
- Open Quick Chat / More Details from that task.
- Start a ChatGPT conversation that already has access to the originating Codex task context.
- Discuss/review/design for several turns in ChatGPT while keeping that Codex context available.
- Use Add to Task / Add this chat to Codex to send the resulting ChatGPT conversation back into the originating Codex task, optionally with a final instruction.
This creates a very useful loop:
Codex task context → ChatGPT discussion/review → return the discussion to the same Codex task
Current mobile limitation
Codex Remote on mobile can open and steer existing Codex sessions, but it does not expose the equivalent context-aware Quick Chat workflow.
A manual workaround such as copying a summary from a normal ChatGPT conversation into Codex Remote is not equivalent, because the ChatGPT conversation did not begin with the originating Codex session context. The important missing step is the first one: launching ChatGPT from the selected Codex session with that task context already attached.
Requested behavior
From a Codex Remote session on iOS/Android, please allow users to:
- open a context-aware ChatGPT Quick Chat from the currently selected Codex task;
- preserve the originating Codex task/session association while discussing for multiple turns;
- review or reason about the task using the same context available to Desktop Quick Chat;
- use Add to Task to append that ChatGPT conversation back to the originating Codex task;
- optionally add a final instruction when returning it to Codex.
Ideally, the workflow and task association should match Codex Desktop as closely as possible.
Why this matters
A common workflow is to let Codex perform implementation or investigation, then use ChatGPT for higher-level review, design decisions, or clarification, and finally return the refined instructions to the same Codex task.
On Desktop this is seamless because both sides share the task relationship. On mobile, losing the initial Codex → ChatGPT context handoff means the user cannot reproduce the workflow while away from the computer, even though the underlying Codex task itself is already accessible through Remote.
This would make mobile Remote much more useful for reviewing and steering long-running Codex work without requiring a desktop just to bridge context between Codex and ChatGPT.
Related issues
I found related reports about the existing Add to Task / ChatGPT-to-Codex workflow and mobile Remote parity, but not this specific feature request:
- #32033 — ChatGPT conversation → Add to Task behavior on Desktop
- #31966 — More Details / Add to Task behavior on Desktop
- #26294 — mobile parity request for Queue / Steer controls
- #40124 — broader session handoff between CLI, web, and mobile
This request is specifically about mobile support for the existing context-aware Codex → ChatGPT → Add to Task loop, rather than generic chat synchronization or copy/paste handoff.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the existing Codex Desktop Quick Chat / More Details → Add to Task flow and the mobile Codex Remote session entry point, then compare how the originating task context is associated. Done means mobile supports the context-aware discussion and returns it to the same Codex task with an optional final instruction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100