goose vs Mirror CLI

goose

Telemetry off until the user opts in, with the collected fields listed. Autonomous mode, which approves every tool call, is the default.

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.

goose

1. Set GOOSE_MODE=smart_approve or approve before a run. The default approves everything, and the first-run prompt preselects Auto
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

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