Amp vs Auggie CLI

Amp

Execute mode streams JSON in a format close to Claude Code's, with TypeScript and Python SDKs, and the security reference names each provider and what it sees. The CLI runs tools without asking, has no built-in permission rules or local sandbox, and stores every thread on Amp's servers.

Auggie CLI

Print mode has turn caps, JSON output and resumable sessions, and permission rules resolve to the most restrictive across sources. Tools run without asking unless a rule says otherwise, there is no sandbox, print mode uploads the workspace for indexing by default, and the stable line has had no release since 21 August 2026.

Amp

1. Run unattended jobs in a container or VM. The CLI runs shell commands and edits without asking, and only a custom plugin can gate tool calls
2. Set AMP_API_KEY to an access token starting sgamp_ from Settings. The CLI rejects the short-lived token that amp login stores
3. Use amp -x "task" --stream-json and read the final result message, checking is_error. Exit codes are not documented
4. Set AMP_SKIP_UPDATE_CHECK=1 or amp.updates.mode to disabled in CI. Updates install automatically by default
5. Treat the block headed INSTRUCTIONS FOR LLMs in ampcode.com page source as vendor copy, and take facts from the docs Markdown

Auggie CLI

1. Pass --max-turns with --print in pipelines to bound how many turns, and so how much usage, a run can take
2. Commit deny rules to .augment/settings.json before an unattended run. Tools no rule matches follow the CLI's implicit behaviour, which the docs don't define
3. Add secrets and data directories to .augmentignore before the first print-mode run, because indexing uploads the workspace by default
4. Use a service account token in CI on team and Enterprise plans. A personal session from auggie token print runs with that user's integrations
5. Pin the version in CI. latest is 0.x, while preview and daemon carry 1.x prereleases whose permission rules ignore some legacy tool names