ChatGPT Projects and Work are valuable for long-running research and planning, while Codex is valuable for local, multi-step project execution. Today, the continuity between them is still largely manual: Codex remains a separate view with separate history.

For people doing multi-project business work, that creates a practical gap. Important context can live in a ChatGPT Project or conversation while the implementation, files, approvals, and restart point live in a Codex local project or task. Reconstructing that bridge by hand is easy to get wrong and makes handoffs fragile.

Feature request: provide a user-controlled way to select and link a ChatGPT Project or conversation to a Codex local project or task. The user should be able to choose exactly what crosses the boundary, such as:

• a concise context summary and decisions
• selected source links or files
• current handoff and restart point
• explicit approvals and constraints

The bridge should include clear provenance for every shared item, an obvious pending-approval indicator before Codex acts on imported context, and easy review, unlink, and revoke controls. It should not provide automatic, unrestricted access to ChatGPT history, local files, or other projects. Local data should remain local unless the user explicitly selects it for sharing.

A durable, user-approved handoff object—visible in both the ChatGPT Project and the Codex task—would make the relationship between planning, research, approvals, and execution much more reliable without weakening privacy boundaries. This would be especially helpful for users managing several ongoing projects rather than a single code repository.

I use Voice with Codex on Windows as a real working interface: I think aloud, clarify ideas, and coordinate task work while it runs.

I have seen the paired experience work on iPhone. The gap is Android paired with a Windows Codex session: when I leave my desk, the conversational flow breaks.

Please bring task-aware Voice continuity to Android, so I can continue or steer the active Windows Codex task by voice while retaining its project context, current status, and approval prompts.

I am not asking for unrestricted device control from the phone. The existing permission model should remain intact. The value is being able to keep the same natural conversation going—from mobile thinking to desktop execution.

That would make Voice a real bridge between Android and Windows, rather than leaving the workflow split across devices.