This repository was archived by the owner on Oct 9, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Oct 9, 2026. It is now read-only.
Validate Codex Lab remote control through ChatGPT GUI #367
Copy link
Copy link
Closed
Labels
planDurable planning issueDurable planning issueplan:donePlan completed or supersededPlan completed or superseded
Description
Finish Line
The current provenance-verified Codex Lab binary completes one bounded end-to-end remote-access workflow through the OpenAI ChatGPT/Codex GUI and a paired remote controller, with durable evidence for session continuity, approval or user input, reconnect behavior, and feature visibility.
Current Status
- State: Complete on July 24, 2026. The official ChatGPT iOS app
1.2026.188on iOS27.0completed the bounded native remote-control workflow against the persistent Codex Lab engine. - Engine evidence: app-server
0.145.0-alpha.27, source commit0d2a292100ca064c13fa226ba9aade1779674ecf, repaired managed-binary SHA-256614783eea9d322d7e9dc266e327e80ccbd5b62c58d46a6e50c0a933b33930dc0, accountinfo@shinycomputers.com, environmentenv_e_6a6004796a40832fba17fbac929a5439, and detached workspace/tmp/codex-lab-issue367-20260724T143757Zat commit85fce13bab87adf7a6e84e47aa536c3d7410deb0. - The iOS Remote UI connected to
Chris-Studio, displayed the mapped projectcodex-lab-issue367-20260724T143757Z, reopened thread019f94c4-2852-7100-a6a8-6b4042613b31, and preserved the prior mapped-worktree Luna turn. - Native approval completed on turn
019f94f6-8575-79c1-99cd-70b6149d8dee: the iOS UI displayed the exact shell command andApprove/Always approve/Denycontrols; a one-timeApprovecreatedISSUE367_IOS_APPROVAL_NATIVE_20260724T162958Z.txt; the turn completed with exact responseISSUE367_IOS_APPROVAL_NATIVE_OK_20260724T162958Z. - Disconnect/reconnect continuity was proven by the earlier
connecting->connectedrecovery canary and merged PR fix(remote-control): honor retries while connecting #468 (85fce13bab87adf7a6e84e47aa536c3d7410deb0). Revocation then removed iOS clientcli_158b30b7c81d43fcaf0087c63d2c3a6a; the authoritative client list changed from one device to zero. - The canary exposed a fatal V8
CodeRangecrash in a signed hardened-runtime engine that lackedcom.apple.security.cs.allow-jit. Re-signing the identical binary with the repository entitlement fixed Luna code mode. PR fix(supervisor): require V8 JIT entitlement #469 added fail-closed install/runtime entitlement validation and merged at124d02c8637525f6fc76f7aadbeb8a38e6634684after all checks and reviews passed. - Verdict: upstream native remote control replaces the core single-thread mobile prompt, mapped-worktree, approval, reconnect, and revocation path. It complements rather than fully replaces the Every Code remote-inbox/WebUI workflow because the native UI exposed
Codex request timed outwhile the engine continued successfully, and this canary did not observe Every Code-specific inbox, multi-agent, or artifact-inspection controls. - Durable evidence, including screenshots, UI source, turn state, V8 crash, engine identity, reconnect logs, client lists, and SHA-256 receipts, is preserved under
~/.codex-lab/supervisor/v1/diagnostics/issue-367-parity-20260724T143757Z. Follow-up supported engine provisioning remains active in Provision signed engine and supervisor through installer #462.
Acceptance Criteria
- Pairing completed and returned controller-visible environment
env_e_6a6004796a40832fba17fbac929a5439. - ChatGPT iOS Remote displayed
Chris-Studio, the mapped project, and the expected durable thread. - Prompt/turn completion was proven from iOS on the same persistent engine thread.
- One-time native command approval completed through the iOS
Approvecontrol and created the exact canary file. - Disconnect/reconnect preserved the environment and thread, including recovery from a stuck
connectingstate through PR fix(remote-control): honor retries while connecting #468. - Revocation removed the iOS client grant; the post-revoke authorized-client list is empty.
- Evidence records iOS app
1.2026.188, iOS27.0, engine source commit and SHA-256, account, environment, workspace commit, thread/turn ids, transport state, and observed capability gaps. - Upstream remote control is recorded as replacing the core single-thread mobile workflow while complementing, not fully replacing, Every Code remote-inbox/WebUI capabilities.
Relationships
- Child of the Codex Lab GUI remote-access dogfood plan.
- Historical source material:
cbusillo/code#387andcbusillo/code#388.
- related: Prove stable native remote control with separate execution auth #381 - Prove stable native remote control with separate execution auth #381
- related: Prove persistent Codex Lab engine behind official Mac and iOS clients #385 - Prove persistent Codex Lab engine behind official Mac and iOS clients #385
- related: Provision signed engine and supervisor through installer #462 - Provision signed engine and supervisor through installer #462
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
planDurable planning issueDurable planning issueplan:donePlan completed or supersededPlan completed or superseded
Activity
shiny-code-bot commentedon Jul 24, 2026
Completed the end-to-end ChatGPT iOS Remote canary on July 24, 2026.
The stock iOS client mapped the detached Codex Lab worktree, continued the persistent thread, approved an exact one-time shell write through the native
ApproveUI, received the exact final response, survived reconnect recovery, and was then revoked with an empty post-revoke authorized-client list. The V8 signing defect discovered during the canary is fixed fail-closed by merged PR #469; supported provisioning remains tracked in #462.Durable evidence:
~/.codex-lab/supervisor/v1/diagnostics/issue-367-parity-20260724T143757Z.