Validate Codex-base Every Code in copied Codex Desktop app

[shiny-code-bot]

Finish Line

The Codex Desktop copied-app flow runs against a Codex-base Every Code binary far enough to submit a real low-risk chat/action, and any remaining protocol gaps are captured as concrete follow-up work.

Current Status

State: Desktop startup compatibility blockers from the first Codex-base copied-app run were addressed by PR #393/#394; full chat/session validation is still open.

Latest evidence:

• PR fix: accept desktop startup app-server probes #393 merged on 2026-06-06 with narrow app-server startup shims for Desktop: remoteControl/status/read, remoteControl/enable, remote_plugin feature enablement, and plugin/list vertical handling.
• PR fix: accept legacy Every Code config shapes #394 merged on 2026-06-06 with legacy Every Code config compatibility, including [tui] alternate_screen = true/false, so real CODE_HOME startup is less likely to fail before Desktop reaches the session surface.
• A post-shim copied-app smoke with a clean temporary CODE_HOME no longer showed the prior unknown-method/schema failures.

Still not done:

• Submit one real low-risk Desktop chat/action against the copied app and current merged code binary.
• Validate externally-created GitHub/LaunchPlane/remote automation session discovery and resume/continue behavior.
• Validate approval/reply/user-input flow for such a session, or document the exact missing replacement keeping Decide remote inbox and Discord UI for Codex-base session continuity #388 open.
• Capture enough logs/screenshots/protocol traces to make the result durable.

Decision:

• Treat PR fix: accept desktop startup app-server probes #393/fix: accept legacy Every Code config shapes #394 as compatibility shims, not a direction change away from Codex-shaped app-server behavior.
• Keep this issue open until the real chat and external-session evidence exists.

Acceptance Criteria

• Build the Codex-base code binary from the selected migration branch.
• Replace only the copied app bundle's embedded binary; never modify /Applications/Codex.app.
• Re-sign and verify the copied app bundle.
• Launch the copied app and confirm the child app-server process is the Codex-base Every Code binary.
• Submit one real, low-risk chat/action manually or with reliable protocol tracing.
• Create or simulate a GitHub/LaunchPlane-origin session and validate discovery/resume/continue behavior in the chosen UI.
• Validate remote approval/reply/user-input flow or document the missing replacement that keeps Decide remote inbox and Discord UI for Codex-base session continuity #388 open.
• Capture app-server logs/traffic for any missing method, shape, event ordering, auth/config, or state behavior.
• Record screenshots/log excerpts and update Combine Every Code with the Codex Desktop app #377 with the result.

Relationships

• Parent: Combine Every Code with the Codex Desktop app #377
• Depends on Plan Codex-base substrate migration for Every Code #384 and Port Every Code identity and config boundary onto Codex base #385 enough to build a coherent code binary.
• Replaces the next-action ambiguity from the feat(app-server): accept Codex Desktop startup calls #383 startup-only copied-app test.

[shiny-code-bot]

Desktop startup compatibility slice smoke-tested on branch feat/desktop-startup-compat.

Evidence:

• ./build-fast.sh passed and produced binary hash 5875b028a287590eb66df5e0000b63e5d582d13bc5cfe5164ef9a848a45b18f8.
• Installed that binary into /Users/cbusillo/Applications/Codex Every Code Current Test.app, re-signed, and verified the copied app.
• Relaunched with clean CODE_HOME=/tmp/code-desktop-home.6ZA79E.
• App-server PID 91267 was launched from the copied bundle and lsof confirmed it used /private/tmp/code-desktop-home.6ZA79E/state_5.sqlite and logs_2.sqlite.
• The previous clean-home blockers are now accepted by app-server: remoteControl/status/read, remoteControl/enable, experimentalFeature/enablement/set for remote_plugin, and plugin/list with Desktop's startup catalog filters.
• Fresh log DB had no ERROR rows. Remaining WARN rows were unauthenticated remote-plugin/cache/manifest warnings from the clean home, not unknown-request/schema failures.

Still open for this issue after this slice: real chat/action validation, externally-created session discovery/resume/continue, approval/reply flow, normal dogfood ~/.code/config.toml compatibility, and code --version identity.