Engineering control

Argos CLI / developer alpha

Your first controlled
Codex Task.

Install the CLI, connect your repository, and declare the work. Argos handles the adapter configuration and checks the control boundary before launch.

Read Quickstart Apply for early access
After package access is confirmed
argos login
argos init
argos run

Before you begin

Bring your repository and your access.

Developer tools

Node.js 18.18 or newer, npm, Git, and a committed repository. The current adapter is designed for the documented macOS/Linux alpha path.

Codex 0.143.0

The supported Codex CLI must be installed and on PATH. Codex authentication is required in the dedicated home.

An invited Argos account

Have your Argos workspace URL and work email ready. The package installation does not automatically grant workspace access.

Shortest working path

Install. Connect. Delegate.

  1. Confirm package access. Then install.

    The command below uses the package name and alpha tag declared by the repository. Public npm availability could not be confirmed. Contact Argos for package access before installation.

    01 / Install after package access is confirmed
    npm install --global @argosbyaurevon/codex-apply-patch-adapter@alpha

  2. Authenticate as a human.

    Use your workspace URL and work email. Complete the existing browser login flow. Human reviewer authority stays separate from the agent key.

    02 / Login
    argos login \
  --app-url https://your-argos-host.example \
  --email you@example.com

  3. Connect the repository.

    Run initialization from your Git repository. It derives paths, prepares isolated local state, and validates the required control components. Follow the Codex login instruction if prompted.

    Continue only after ARGOS CONTROL BOUNDARY ACTIVE.

    03 / Initialize
    cd /path/to/repository
argos init

# Required readiness output:
# ARGOS CONTROL BOUNDARY ACTIVE

  4. Declare a Task.

    Run interactively to provide an objective and EXPECTED, REVIEW, and PROTECTED paths. The verification plan is frozen before controlled work begins.

    04 / Controlled Task
    argos run

# Declare the objective and path scope.
# Start controlled Codex.
# Inspect execution and verification separately.

From setup to evidence

What the CLI handles for you.

  • Derives repository and installed adapter paths.
  • Creates or reuses the scoped project, agent, and integration channel.
  • Stores generated state and credentials outside the repository.
  • Configures the dedicated Codex home and required hooks.
  • Checks control-boundary readiness before launch.
The documented launch uses a dedicated CODEX_HOME, workspace-write sandbox, no native approval prompt, and the required hook-trust bypass. Argos review remains enforced by the installed hooks.

Current alpha: one existing-file apply_patch update per operation; process-bound REVIEW continuation; deterministic verification of the declared contract.

Read the launch security model