Developer quickstart

This path connects a local terminal to Atoi without copying an operator token into client configuration.

#1. Install

The current CLI package requires Node.js 22 or newer.

curl -fsSL https://atoi.app/install.sh | bash
atoi version

The installer selects a supported package manager and installs @creative-int/atoi-cli. Review the script before running it when your environment requires that policy.

#2. Authorize

atoi account login
atoi account status --json

Complete the browser device flow and confirm the code shown in both places. The CLI stores a revocable operator identity locally and exchanges it for short-lived access at runtime.

#3. Verify health

atoi status --json
atoi doctor --json
atoi mcp status --probe --json

Keep configuration, connectivity, and governed MCP probe results separate. A local executable alone does not prove account or backend access.

#4. Resolve a Project

atoi project list --json
atoi project status <project-id> --json

Reuse a Project whose identity and source match. Create one only when no durable boundary exists:

atoi project create --name "My app" --repo owner/repository --branch main --json

#5. Start and inspect a Task

atoi task start \
  --project <project-id> \
  --profile safe \
  --place cloud \
  --prompt "Audit the current release state and return evidence." \
  --json

atoi task wait <task-id> --json
atoi task changes <task-id> --json

Use safe for inspection. A write-capable profile can prepare changes, but it does not silently authorize apply, publication, or another permanent gate.

#6. Configure a coding client

atoi mcp config --client codex

The generated configuration launches atoi mcp serve; it contains no bearer token. See MCP and plugins for other supported clients and the three governed tools.

#Completion check

You are ready when account status is connected, the MCP probe passes, the intended Project source is legible, and a Task returns a literal state plus Result, Changes, Checks, and Proof. Continue with the CLI reference.