codex-dev-native
/codex-dev-native — delegate-to-codex development loop (native engine)
Engine = the official Codex plugin's codex-companion runtime (plugin codex@openai-codex). Claude does NOT hand-roll dispatch, background execution, job tracking, or status/result plumbing — the native per-repo registry owns that. (One limit to know up front: native jobs are session-scoped — they don't survive the Claude session ending; see Step 4.) Claude's job is the orchestration + governance shell around it: decompose, isolate, dispatch, accept, review personally, rework, merge. The flow advances on its own and only stops to ask the user when BLOCKED, when a merge conflict needs a ruling, or when something would cross the role boundary. Report a one-line progress update on every task state change.
Restrictions follow exactly what the native engine enforces, plus brief red-lines for the rest. codex runs under workspace-write — the only sandbox codex-companion gives a write task: the OS confines writes to its cwd and blocks escape, and network is on so codex can fetch docs / install project deps (this is what removes the offline pain). Anything the sandbox does NOT cover — no git writes, the write-scope allowlist within the cwd, no global installs — is enforced through the brief's hard constraints + post-hoc verification. Never pass danger-full-access.
Native vs Claude — never rebuild the native side
| Concern | Owner |
|---|---|
| launch codex, background exec, running/stuck/done state, fetch result, cancel, resume-same-thread | native codex-companion — task / status / result / cancel / task --resume-last |
| job tracking within a session (across turns) | native — status / result / status <id> --wait over the per-repo registry; not cross-session — SessionEnd terminates the session's jobs (see Step 4) |
| decompose & tiers, concurrency decision, worktree isolation, mechanical acceptance, personal review, rework loop, merge | Claude |