Decide remote inbox and Discord UI for Codex-base session continuity

[shiny-code-bot]

Finish Line

Every Code has a deliberate decision for remote inbox / Discord UI in the Codex-base port, based on whether Codex Desktop can discover and continue sessions created by GitHub/LaunchPlane/remote automation paths.

Current Status

State: Preserve backend; Desktop replacement remains unproven even though startup compatibility improved.

Latest #387 signal:

• PR fix: accept desktop startup app-server probes #393 addressed the Desktop startup app-server gaps previously listed here: remoteControl/status/read, remoteControl/enable, remote_plugin feature enablement, and plugin/list vertical handling.
• PR fix: accept legacy Every Code config shapes #394 addressed a real-user-home config blocker that could prevent Desktop from reaching session behavior.
• A clean-home copied-app smoke after those shims no longer showed the prior unknown-method/schema failures.

Decision state:

• Do not remove remote-inbox backend capability.
• Do not drop Discord-specific presentation yet.
• Desktop is still only a candidate replacement for remote-inbox/Discord flows until it proves externally-created session discovery, resume/continue, and approval/reply/user-input handling.

Concrete validation bar before marking Discord UI removable:

• Desktop can discover an externally-created session with origin metadata.
• Desktop can resume/continue that session.
• Desktop can handle at least one approval/reply/user-input flow for that session.
• Evidence is captured in Validate Codex-base Every Code in copied Codex Desktop app #387 with logs/screenshots or protocol traces.

Next action:

• Rerun copied-app validation from Validate Codex-base Every Code in copied Codex Desktop app #387 using the current merged binary and an externally-created session fixture.

Acceptance Criteria

• Map all current remote-inbox/session-continuity paths: GitHub label/LaunchPlane origin, remote inbox bridge, Cloud Tasks, TUI session catalog/resume, and Discord reply/approval paths.
• Preserve remote-inbox backend capability until a replacement path is validated.
• Determine whether Codex Desktop can replace Discord UI for GitHub/LaunchPlane-created sessions.
• Do not remove Discord-specific remote-inbox presentation until Desktop or another UI can discover, resume/continue, and handle approval/reply flow for externally-created sessions.
• Persist or otherwise expose session origin metadata needed for GitHub/LaunchPlane-created sessions across restart.
• Validate by creating or simulating a GitHub/LaunchPlane-origin session, discovering it, resuming/continuing it, and handling approval/reply flow through the chosen UI.
• Update Inventory and port Every Code features onto Codex base #386 with the final keep/drop/defer decision.

Relationships

• Parent: Inventory and port Every Code features onto Codex base #386
• Related to Combine Every Code with the Codex Desktop app #377 and Validate Codex-base Every Code in copied Codex Desktop app #387 because copied Desktop validation should include externally-created session continuity if Desktop is meant to replace Discord UI.
• related: Validate Codex-base Every Code in copied Codex Desktop app #387 - Validate Codex-base Every Code in copied Codex Desktop app #387

[shiny-code-bot]

Related #387 update: Desktop startup compatibility improved, but this issue should remain open.

The copied Codex Desktop app now starts cleanly against the Codex-base Every Code app-server with the prior protocol/schema blockers shimmed or accepted (remoteControl/status/read, remoteControl/enable, remote_plugin feature enablement, and plugin/list vertical). That moves Desktop closer to being the preferred GUI.

It does not yet prove Desktop can replace Discord/remote inbox for GitHub/LaunchPlane-created sessions. We still need the externally-created session fixture path, discovery/resume/continue validation, and approval/reply/user-input validation before removing Discord-specific presentation or remote-inbox backend capability.