Skip to content
Browse documentation
Controlled alphaValidatedClaude Code / Cursor · In development

Argos developer documentation

Developer Quickstart

Connect the released Codex workflow, declare one assignment boundary, and follow a controlled Task into verification and Evidence.

1. Create the Argos project

  1. Create an Argos account and verify the email.
  2. Create a workspace and first project in onboarding.
  3. Use a committed Git repository on a trusted developer host with Node.js 22 and the chosen agent CLI.
bash
# Founder-assisted source alpha: use matching artifacts supplied by Argos.
npm install --global   ./argosbyaurevon-sdk-0.1.0-beta.2.tgz   ./argosbyaurevon-codex-apply-patch-adapter-0.1.0-alpha.1.tgz
argos --help

2. Authenticate and connect

bash
cd /path/to/repository
argos login
argos init

Browser OAuth authenticates the human. Initialization binds the current repository and prepares the validated Codex path.

OpenAI Codex setup →

3. Start a Guarded Task

Start tracking in one terminal, keep it open, then launch the controlled Task in a second terminal.

bash
argos start
# Copy sessionId from the JSON response.
bash
argos run   --tracking-session <session-id>   --objective "Add password reset rate limiting"   --expected "src/auth/password-reset/**"   --review "src/shared/**"   --protected "src/auth/session/**,package.json,.env*"

Argos freezes the goal, scope and verification plan before execution. When checks exist, declare the files and directories defining them, such as package.json, tsconfig.json, tests and scripts.

4. Review the result

  1. An expected supported edit continues under the existing policy.
  2. An unexpected supported edit is held for approval; open Needs approval and decide the exact action.
  3. Let the agent finish normally.
  4. Open the Task and Evidence links printed by the CLI.
  5. Inspect authorization, execution, reconciliation, and verification separately.
  6. Stop tracking with argos stop --session-id <session-id>.