Verified source / limits, 3 November 2026

Remote observed standard app: OpenAI.Codex 26.1027.3384.0, CLI
0.166.0-alpha.5.1. Installed custom app: Sam.CodexControl 26.1007.2314.2,
config appVersion 26.1007.21434. Current running versions require re-verification.
Native standard profile reported: %APPDATA%\Codex\web\Codex.
Custom candidate isolated desktop profile: %USERPROFILE%\.codex-control-ahmed-desktop.
Candidate CODEX_HOME: %USERPROFILE%\.codex-control-ahmed (not proved to contain
original history). The candidate was never proved to start or own original chats.

OpenAI documents CODEX_HOME as local config/state/history storage:
https://learn.chatgpt.com/docs/config-file/config-advanced
Official app-server thread/read reads a stored thread without resuming it;
thread/list pages stored threads, with section/source/account filters and archived
state relevant to missing sidebar items:
https://learn.chatgpt.com/docs/app-server

Matching downloaded CLI source is retained in ../standard-cli-source-0166 with
SOURCE-RECEIPT.json (official rust-v0.166.0-alpha.5.1, commit f79b26c).
Its queue command can implicitly fall back to an embedded server. Do not use that
path to find a desktop owner. An explicit --remote unix:// endpoint attaches to
an existing server, but the actual remote desktop endpoint/ownership has not been
established. daemon version's no-start probe is not evidence that it is the
visible desktop's owner. No new CLI query/queue or fallback is performed here.

Required Ahmed-side supported checks:
1. Identify the original running app, selected account/project and original
   CODEX_HOME through its supported APIs/configuration. Read/list the exact
   existing coordinator ID; check archived and UI filters before any migration.
2. Verify actual app/backend versions and whether original store compatibility
   permits any custom consumer. No compatibility guarantee was found for opening
   a newer standard app's store with the older custom backend. Retain the original
   owning version where uncertain. No raw DB edits, rollout edits, profile/token
   copying, resets, second backend or duplicate chat.
3. Restore visibility in the owning UI using supported filters/config/history
   actions and verify every original ID/project is retained. No blanket unarchive.
4. Verify the app-owned supported endpoint and exact coordinator. The supplied
   binding adapter supports the existing Codex Control task/rpc endpoint ONLY if
   that same visible owner actually exposes it. Otherwise source-check the actual
   app's supported API; do not invent a host, port or token resolver.
5. Reuse an existing pending handoff, observe it in the original visible chat and
   return one substantive reply. An API acceptance or mailbox receipt is not
   desktop rendering. Do not add another challenge or handoff while existing IDs
   f098178e-c0e9-451d-b094-2b38bbcaddfe and da193840-c2d6-489d-9d82-d4f1dad71301
   remain pending. Record turn, visible observation and returned reply separately.

The prior automatic-review rejection of remote EWS server launch and the old
custom-startup capture action remain respected. This package attempts neither.
