Amp vs Droid 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.

Droid CLI

droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, and usage metrics go to Factory by default.

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

Droid CLI

1. Set FACTORY_API_KEY (starts fk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser
2. Start with droid exec and no flags for analysis. Add --auto low for edits and --auto medium for installs, tests and local commits
3. Use --output-format json and read is_error, num_turns and session_id. Treat a non-zero exit code as failure
4. Set sandbox.enabled to true before running on untrusted code. In droid exec a sandbox violation is denied without a prompt
5. Pin the version in CI with npm install -g droid@<version>, or set FACTORY_DROID_AUTO_UPDATE_ENABLED=false on standalone installs, which update themselves