Feature request: event delivery into an existing local Codex Desktop chat

[ArunGupta25]

Problem

An external application can receive an asynchronous result for a request initiated in a local Codex Desktop conversation. It needs to return that result to the same already-open chat without periodic model polling or launching a second competing app-server session. Today, MCP Events documents Work chats with Cloud selected and dots, while the app-server thread/resume documentation does not define attachment to the desktop app's live chat, busy turn, approval state, or notification lifecycle.

Requested capability

A supported, authenticated event input for an existing local desktop thread, with:

• Platform-attested account, host, and thread binding so payloads cannot nominate arbitrary chats.
• Stable event IDs, idempotent duplicate handling, immutable receipt time, and a queryable receipt distinguishing accepted, queued, visible in chat, and processed.
• Defined behavior while the chat is busy, awaiting approval, offline, closed, or restarting. Delivery should not interrupt a turn or create a second session.
• Reconciliation after uncertain submission, without blind replay or silent loss; visible errors for wrong destination or rejected events.
• Preservation of the original history, permission profile, and unread/update state. Event content should be treated as data, not new authority.
• Event-driven delivery rather than periodic model polling.

Acceptance test

In an isolated existing local desktop chat, submit a synthetic event and verify exact-thread UI readback and receipt. Repeat with the same event ID, a wrong account/thread, a busy turn, an approval wait, app downtime, and restart. Confirm one visible result after recovery, no competing session, and unchanged permissions.

Is there already a supported interface for this? If not, please consider this as a Codex Desktop platform capability. The current documented surfaces are MCP Events and Codex app-server.