Cline vs goose

Cline

Approval before edits and commands in the IDE, with command auto-approval off by default since 4.0.0. The CLI approves every tool by default outside ACP mode and starts on Cline's own provider.

goose

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

Cline

1. Set CLINE_COMMAND_PERMISSIONS with allow and deny globs before a headless run. The CLI approves every tool by default
2. Pick a provider with -P and a key, or run cline auth. The default provider needs a Cline sign-in
3. Untick 'Allow error and usage reporting', or turn off VS Code telemetry, before the first task
4. Pin the CLI version. 2.3.0 was a malicious publish
5. Keep the hub on 127.0.0.1 or set ROOM_SECRET, and run 3.0.30 or later

goose

1. Set GOOSE_MODE=smart_approve or approve before a run. The default approves everything
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