Prime Agent vs Mirror CLI

Prime Agent

Budgets for turns, tokens and time bound an autonomous run, and sessions survive a closed terminal through a supervising daemon. Model-written Python and shell commands run with the user's rights, with no approval step and no sandbox, and the Rust build on the main branch ships only as nightly betas.

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.

Prime Agent

1. Run it in a disposable clone, container or VM. It executes model-written Python and shell commands with the user's rights and asks nothing first
2. Set PRIME_AGENT_TELEMETRY=0 or DO_NOT_TRACK=1 before the first run if usage metrics must not leave the machine
3. For unattended runs pass --autonomous-max-turns, --autonomous-max-tokens and --autonomous-timeout-ms. Reaching a limit does not mean the task succeeded
4. Headless use is -p with --mode json per the argument parser. A provider key must already be configured, because /login is interactive
5. The -t/--tools, -nt/--no-tools and -nbt/--no-builtin-tools flags were removed and now fail as unknown options

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