Amp vs Rovo Dev 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.

Rovo Dev CLI

Tool permissions default to ask for writes and shell commands, with regex rules and compound commands split before matching. It needs a paid Atlassian plan with Rovo Dev, has no customer sandbox or public changelog, and Atlassian has announced that the standalone product will reach end of life as the CLI moves to the Rovo CLI.

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

Rovo Dev CLI

1. Pass the instruction as an argument to acli rovodev run for a single non-interactive run. No JSON output flag or exit codes are documented
2. Use acli rovodev serve <port> and stream /v3/stream_chat?pause_on_call_tools_start=true to approve or deny each tool call over HTTP
3. Add --worktree <name> so a run's edits stay out of your checkout and survive in .rovodev/worktrees/<name>
4. Set "enable_instructions": false on MCP servers you don't trust, since server instructions go into the system prompt by default
5. Check /usage before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on