Cline vs Mistral Vibe CLI

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.

Mistral Vibe CLI

Apache-2.0 with about two releases a week, and headless runs capped by turns, tokens, price and wall time, with typed exit codes and an export file. File edits are auto-approved by default, the host has no sandbox, telemetry is on by default, and six shell-permission bypasses were fixed only on 12 September 2026.

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

Mistral Vibe CLI

1. Pass --agent on every -p run (plan is read-only). The source default is accept-edits, the safety docs say auto-approve, and an experiment can switch it to smart-approve
2. Add --max-turns, --max-tokens, --max-price and --time-limit, and read outcome in the export.json that --output-dir writes. Exit 3 means a limit or a refusal
3. Run in a container or behind --agent-socket before using --auto-approve. Vibe has no sandbox of its own on the host
4. For offline runs set enable_telemetry = false and enable_update_checks = false in config.toml. The docs' enable_auto_update isn't the key the code reads
5. Use 2.25.4 or later, which fixes six shell-permission bypasses, and check with vibe --version