# test750 — Codex TUI one-command create/start/resume journey

Date: 2026-08-21 (Asia/Shanghai)
Source: feat/codex-copresence-interactive (pre-merge Docker verification)
Environment: isolated Docker container; no host Codex or anet state mounted

Command:

    sg docker -c 'docker build -t anet-test750 -f tests/test750-codex-copresence-onecommand/Dockerfile . && docker run --rm anet-test750'

Result: PASS — 10 groups, 0 failures.

- L0 isolated environment: PASS
- L1 profile, preflight, dependency, and runtime-alias decisions: PASS (80 assertions)
- L2 explicit flag, `codex-cli` alias, and a real PTY runtime-picker selection all persist co-presence: PASS
- L3 plain `anet node start <name>` routes a recorded node to the TUI stack: PASS
- L4 one-off `--copresence` remains compatible and is remembered: PASS
- L5 read-only default and explicitly remembered full-access posture: PASS
- L6 missing dependencies are reported together: PASS
- L7 unreachable remote Hub is never replaced by a local Hub: PASS
- L8 incomplete startup exits non-zero and names the failed step: PASS
- L9 register/login failures stop the first-run chain: PASS

The PTY test moves through the actual Inquirer runtime menu with arrow keys and Enter. Choosing the user-facing `codex-cli — Codex 共存 TUI` row writes `runtime: codex-app-server` plus `codexCopresence: true`. Resume uses the same plain `node start` path after stop/interruption.
