Mirror CLI vs Rovo Dev CLI

Mirror CLI

Mirror CLI is Apache-2.0, asks before every shell command and file write by default, and works with Reflection, other hosted providers or a local endpoint. It is a one-day-old 0.1.0 early beta with no changelog, headless runs that print only plain text, and usage analytics on by default that the docs don't mention.

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.

Mirror CLI

1. Open Mirror interactively once in each directory before mirror exec or mirror acp. Both refuse to run until the usage and folder notices are accepted
2. Pass --approval-mode auto to mirror exec only inside a container or VM. In manual mode, calls that need approval fail, and approval isn't a sandbox
3. Set --max-iterations on unattended runs. Turns are unlimited by default
4. Check the result with your own tests. exec returns 0 whenever it prints an answer
5. Never share logs recorded with --log-level debug. The docs say they contain request headers with the API key

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