Skip to content

Unify phone execution and preserve host-specific safeguards - #104

Draft
gofenix wants to merge 1 commit into
codex/runtime-viewer-corefrom
codex/runtime-phone-core
Draft

gofenix wants to merge 1 commit into
codex/runtime-viewer-corefrom
codex/runtime-phone-core

Conversation

@gofenix

@gofenix gofenix commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Both adapters now use one phone controller, device discovery, action validation and execution-state implementation. WorkBuddy injects its existing pixel sampling, pre-dispatch validation and read retries; Codex retains its existing image pipeline.

Typed failures survive the Codex daemon/CLI boundary. An action whose result cannot be confirmed is reported as outcome_unknown, without replaying it.

Validation: shared fault-injection contracts and both host checks passed. This draft is stage 2 of 4, based on the shared viewer branch. Device locks remain per host instance; concurrent control of the same phone across hosts is unsupported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants