Pi vs Mistral Vibe CLI

Pi

Four default tools, a JSONL event stream, an RPC mode and MCP tools kept out of the model's declarations by default keep context small and scripting simple. Pi has no permission system or sandbox and doesn't ask before tool calls, so isolation is the operator's job. Version 1.0.0 is dated 1 October 2026.

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.

Pi

1. Run Pi inside a container or VM for unattended work. It has no sandbox and doesn't ask before running shell commands
2. Use pi --mode json and wait for agent_settled. A failed response doesn't set a nonzero exit code in JSON mode
3. Split the JSONL stream on LF only. Node's readline also splits on U+2028 and U+2029, which are valid inside JSON strings
4. Pass --no-approve or --approve in scripts to make the project trust decision explicit
5. Set PI_TELEMETRY=0 and PI_SKIP_VERSION_CHECK=1, or PI_OFFLINE=1, to stop the default requests to pi.dev

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