Feature request: idempotent task creation and explicit phone ↔ Codex Desktop ownership handoff

What variant of Codex are you using?

Codex App + ChatGPT iPhone Remote + local app-server automation

What feature would you like to see?

I have a concrete cross-device automation use case that would benefit from first-class support.

An iPhone Voice Memo syncs to an always-on Mac, where a local daemon detects it, transcribes it locally, and generates a Codex prompt. The daemon then needs a supported way to create one official Codex task that is immediately visible in the ChatGPT/Codex iPhone app while the Mac is locked but awake and online. Later, the user should be able to continue that same task in Codex Desktop, and then continue it again from the phone.

The difficult part is not transcription. It is task creation, mobile visibility, and thread ownership across Codex hosts. In current experiments, using a standalone app-server/Remote host can make the task visible on mobile, but attaching or continuing the same thread from Codex Desktop may lead to an active-writer or “opened in another app” conflict. Recovering requires an explicit release/resume sequence.

Requested capabilities:

• A supported local API for idempotent task creation, returning the canonical thread ID and a durable receipt.
• Immediate mobile visibility/notification for a newly created task.
• Explicit atomic ownership handoff between the mobile Remote host and Codex Desktop.
• A visible owner/state indicator and fail-closed handling of conflicting writers.
• Safe sequential continuation on phone → Mac → phone without duplicate turns, forks, or manual database changes.

Simultaneous multi-writer editing is not required. A reliable sequential handoff would fully satisfy this workflow.

Additional information

Related context: #31114, #35800, #37620, and discussion #14067.

This request focuses on a supported creation-and-ownership protocol rather than transcription. Identifying account, host, environment, local path, recording, and thread details have intentionally been omitted from this public report.

Start by reviewing related issues #31114, #35800, #37620 and discussion #14067, then trace the local app-server task-creation and host-ownership entry points. The work is done when supported idempotent creation, canonical receipts, mobile visibility, and explicit sequential phone-to-Desktop-to-phone handoff prevent duplicate turns, forks, and conflicting writers.