goose vs mini-swe-agent

goose

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

mini-swe-agent

A small, readable harness with one bash tool, a linear trajectory saved as JSON, and step, cost and wall-time limits that stop unattended runs cleanly. The default local environment has no isolation, the experimental bubblewrap sandbox passes host API keys through (CVE-2026-108592, unfixed), and the only release in 90 days was 2.4.6 on 23 July 2026.

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

mini-swe-agent

1. Run with -y --exit-immediately for unattended use. Without --exit-immediately it waits for input when the agent finishes
2. Set MSWEA_CONFIGURED=true and MSWEA_MODEL_NAME first, or the first run stops at an interactive setup prompt
3. Read info.exit_status in the -o trajectory file. A run that hits its limits still exits normally
4. For untrusted repositories use -c mini.yaml -c environment.environment_class=docker -c environment.image=<image>. The local and bubblewrap environments both expose host variables
5. Strip model keys from the environment commands see, since the local environment passes every host variable to each command