Amp vs goose

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.

goose

Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the 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

goose

1. Set GOOSE_MODE=smart_approve or approve before a run. The default approves everything
2. Pass --max-turns with a real limit. The default is 1000
3. Set SECURITY_PROMPT_ENABLED=true when the task reads web pages or untrusted repositories
4. Use --output-format json and --no-session in CI, and check the exit code
5. Point remotes and links at aaif-goose/goose and goose-docs.ai. The block/goose paths redirect