Login and setup
argos command not found
What it means: The public CLI package is not installed on the active npm global prefix.
What to do: Install @argosbyaurevon/codex-apply-patch-adapter@alpha globally, then run argos --help.
Not logged in or session expired
What it means: The human session cannot be refreshed.
What to do: Run argos login again and explicitly authorize the CLI in your browser.
Repository not initialized
What it means: No matching repository configuration exists under ~/.argos.
What to do: Run argos init from a committed Git repository.
Invalid scope
What it means: A path is absolute, escapes with .., or does not match tracked expected/review files.
What to do: Use repository-relative tracked paths and rerun argos run.
Argos API unavailable
What it means: The configured host did not answer the safe setup or runtime request.
What to do: Confirm the supplied host is running and reachable, then retry. Do not bypass the adapter.
Control boundary
Unsupported Codex version
What it means: The alpha readiness check did not find Codex CLI 0.143.x.
What to do: Install the supported 0.143.0 alpha version and rerun argos init.
ARGOS CONTROL NOT ACTIVE
What it means: A required hook, path, credential, service, reader, or verifier check failed.
What to do: Fix the exact named component and rerun initialization. Controlled Codex was not started.
Missing Codex configuration
What it means: The generated isolated CODEX_HOME is absent or invalid.
What to do: Rerun argos init. Do not copy hooks manually into your normal Codex home.
Review and reconciliation
REVIEW is waiting
What it means: The exact mutation is held and the repository is unchanged.
What to do: Use A or D in the active argos run terminal, or open the protected Task link for context.
Review process was interrupted
What it means: Current continuation is process-bound and cannot claim safe automatic resumption.
What to do: Inspect Task/Evidence state, reconcile repository state, and start a new controlled Task when safe.
PostToolUse result is missing
What it means: The mutation may have run but result recording was not confirmed.
What to do: Do not repeat the patch blindly. Inspect the repository and Task evidence, then reconcile the ambiguous outcome.
Verification outcomes
Task FAILED
What it means: A deterministic required condition was conclusively false.
What to do: Open Evidence, fix the named engineering failure in a new controlled Task, and rerun the frozen checks.
Task UNCERTAIN
What it means: The verifier could not reliably establish truth because its environment or configuration failed.
What to do: Restore the missing executable, readable state, timeout budget, or configuration, then verify again without weakening the plan.