Head to head · Agent harnesses · October 2026 research run
Click vs Mistral Vibe CLI
Mistral Vibe CLI scores 62.1 (B) on agent readiness against Click's 48.6 (D), and leads in every scored category. Both do agent harnesses.
Best agent harnesses and coding agents · All 1767 harnesses comparisons
Which one, for what
Click D
Best for Product teams that want to embed an agent per customer, ticket or document without running the loop, sandbox or browser themselves, with any model.
Also in its favour
- A hosted endpoint, with nothing to install
- No incidents deducted, where Mistral Vibe CLI loses 14 points for them
Watch for
No status page, SLA or public changelog found
Best for Developers and CI jobs that want an open-source harness tuned for Mistral models, with hard per-run budgets and an export file, or a local model with no account.
Ahead on
- Reliability, 69 against 35
- Agent ergonomics, 84 against 79
- Security & auth, 58 against 41
- Payments & pricing, 90 against 15
- Maintenance & community, 73 against 25
- Transparency & trust, 81 against 44
Also in its favour
- Free to start without a card
- Open source
Watch for
The default agent auto-approves file edits, and there's no sandbox on the host. Isolation needs the experimental --agent-socket server or a container
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing Mistral Vibe CLI +75
Click 15
No x402, MPP or L402. The only 402 is card_verification_required (0). Plan prices are public, Free at $0 and Pro at $199 a month with stated allowances, but no per-unit price (15). The Free plan exists, but writes return 402 until a card is verified in the dashboard (0). A person signs up in a browser, verifies a card and creates the key (0). 0 + 15 + 0 + 0 = 15.
Mistral Vibe CLI 90
Harness reading of the published rubric, as for openai-codex and qwen-code. No payment protocol (0). Plan prices (Pro $14.99 a month, Team $24.99 a user a month) and per-token API prices for the default model ($1.5 and $7.5 per million) are public without a login (20). A Free plan includes limited coding sessions, and the docs document a fully offline set-up with a local model and no Mistral account. Whether the Free plan asks for a card wasn't checked (20). An agent can install the CLI and run it against a local OpenAI-compatible server with no sign-up, since a llama.cpp provider on 127.0.0.1:8080 is in the defaults (20). 0+20+20+20 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community Mistral Vibe CLI +48
Click 25
Closed service with no dated changelog. The newest first-hand date is API version 2026-10-19, 30 days before this check, read as within 90 days rather than within 30 since nothing says what shipped then (20). No dated release entries to count (0). Support is by email to the founder, per the terms. No public changelog, issue tracker or community channel was found (5 of 15). No official SDK (0). No public package or CI to check (0). 20 + 0 + 5 + 0 + 0 = 25.
Mistral Vibe CLI 73
3.0.4 on 30 October 2026 (30). 21 release tags from 4 August to 2 November, 2.24.0 to 3.0.4, each with a dated changelog entry (20). The 18 October issue and pull request counts came from shields.io badges, a third-party copy of GitHub data this run bars, so they are struck. Response times couldn't be read. CONTRIBUTING.md says the project isn't accepting contributions, and the history is squashed release commits. Credit is for the dated changelog, the issue templates and the public advisory (8 of 25; 10 on 18 October with the counts). No SDK. vibe-acp is current in the ACP registry at 3.0.4 and the Homebrew formula is at 3.0.4 (8 of 15). Dependencies are pinned to exact versions, workflow actions are pinned by commit, and CI runs on main, but no Dependabot or Renovate config was found (7 of 10). 30+20+8+8+7 = 73.
Transparency & trust Mistral Vibe CLI +37
Click 44
Closed service under terms based on the Common Paper Cloud Service Agreement 2.1, dated 12 October 2026, under Delaware law (15 of 30). The privacy statement lists what is collected, names PostHog with session replay for the website and dashboard, and says staff may access service content for support and to improve the service. Retention is "as long as reasonably needed" with no periods. The docs say Click-created sandboxes are deleted with their session (10 of 30). No deprecation policy. The terms promise 30 days' notice of price changes (3 of 20). Providers are described by category, with PostHog the only one named, and processing in the United States and other countries (5 of 20). 15 + 10 + 3 + 5 = 33.
Mistral Vibe CLI 81
Apache-2.0, with LICENSE and pyproject in agreement (30). The README sends readers to Mistral's privacy policy (effective 3 September 2026), which names Vibe. The commercial terms (effective 25 September 2026) say no training on customer data unless a product's default or an opt-in allows it, and the pricing page lists model training as opt-out on Free, Pro and Team. The configuration reference calls telemetry anonymous without listing its fields. The offline guide now names enable_update_checks = false with enable_telemetry = false, as the source reads them (16 of 30; 14 on 18 October, when it named a key the source defines but never reads). Removals are listed in the changelog, deprecated settings are named in the configuration reference and warned about at startup, the agent socket may change without notice, and custom Python tools and the bundled local model were removed in patch releases with warnings (10 of 20). Telemetry is disclosed with an opt-out in the README and the configuration reference, and the README names the server-managed shell-tool rollout, but its fields are only in the source (14 of 20). 30+16+10+14 = 70.
Reliability Mistral Vibe CLI +34
Click 35
Hosted lines, for the HTTP API. No status page is linked from the site or the docs (0), so no incident history could be read (5). Concurrent session limits are published per plan (2 on Free, 50 on Pro) with body size limits of 16 MiB, but no request rate limits were found (8 of 15). 429 concurrency_limit_exceeded and the 503 codes are documented, the conventions say to retry 503 after a short wait, and request_id makes submissions safe to retry. No Retry-After header is documented (12 of 15). No SLA in the terms, which leave usage limits to Click's discretion (0). The API carries no beta or preview label (10). 0 + 5 + 8 + 12 + 0 + 10 = 35.
Mistral Vibe CLI 69
Local-package reading. PyPI, uv, pip, Homebrew at 3.0.4 and an install script, with Python 3.12 or later stated and UNIX the supported target (20). A public CI workflow on push and pull request to main runs pre-commit, the test suite and a build and install smoke matrix, but GitHub's pages and API were refused in this session, so whether main is passing is unchecked (15 of 25). The 18 October issue counts came from shields.io badges, a third-party copy of GitHub data this run bars, so they are struck. Every release has a Fixed section in the changelog, and how many open issues are crashes or regressions, and how fast they're answered, couldn't be read (10 of 25). The changelog states Keep a Changelog and semver and marks breaking changes, but the hooks rename shipped in minor 2.21.0, patch 2.11.1 changed the -p approval default, patch 2.26.1 removed the bundled local model, and patches 3.0.3 and 3.0.4 carry marked config, model and session breaks (9). 3.0.4, classified Production/Stable (15). 20+15+10+9+15 = 69.
Security & auth Mistral Vibe CLI +17
Click 41
Platform API keys are revocable, but each has full access to its tenant, including key management. The MCP server's OAuth tokens through WorkOS carry scopes for the MCP endpoint only (20 of 30). Tool grants limit each agent to named tools, and sessions can override grants, but approvals are left to the customer's application and no read-only key was found (8 of 20). Agents read web pages, browser content and MCP results. The docs tell users to keep secrets out of messages and keep MCP tools from returning stored secrets, but give no prompt-injection guidance (3 of 15). Every top-level and nested tool call is recorded and listed per session, and webhook deliveries can be listed (10 of 15). No security.txt (404), disclosure policy or certification found (0). 20 + 8 + 3 + 10 + 0 = 41.
Mistral Vibe CLI 58
Framework reading (telemetry defaults, approvals, guardrails, sandboxing), five lines. Telemetry and crash reporting are on by default with an opt-out, and the source sends tool names, approval decisions, the model and file counts to api.mistral.ai only when a Mistral key is set. Telemetry also turns on GrowthBook experiments, and one of them (vibe_cli_smart_approve_default) can make smart-approve the default. Credentials are Mistral keys in an environment variable, a plaintext ~/.vibe/.env or the keyring, workspace-scoped with optional expiry per the mistral-api listing, and MCP servers can use OAuth (12 of 30). Five agents with a read-only plan agent and bash allow and deny lists, a prompt for access outside the working directory, outside_workdir = "deny" (3.0.3) to refuse it outright, an admin enable_auto_approve = false (3.0.1) that forbids auto-approve, and pre_tool hooks that can deny calls. The default auto-approves file edits, and there's no sandbox on the host (13 of 20; 11 on 18 October, before the two settings). Project config, hooks and MCP servers load only from trusted folders, and -p needs --trust to load them. The safety page warns that smart-approve isn't a sandbox. No network egress control on the host, and MAI-2026-003 says injected instructions could trigger the bypassed commands (8 of 15). OpenTelemetry tracing is opt-in, with default, strict and no redaction, and each run can write a session journal and an export with the effective config. Managed admin config exists, and audit logs come with the Enterprise plan (13). SECURITY.md asks for private reports, security.txt is valid (expires 5 May 2027) and links a HackerOne form, and Mistral publishes dated advisories with CVEs, three to 2 November. No bounty terms or certification report were read, so 12, as mistral-api and mistral-voxtral-transcribe take on the same Mistral pages (14 on 18 October). 12+13+8+13+12 = 58.
Agent ergonomics Mistral Vibe CLI +5
Click 79
Entries can be read by min_entry_id and max_entry_id, get_state returns one snapshot, and lists take limit, so responses stay small (20 of 25). Cursor pagination on every list, with filters such as archived, type and category that must stay fixed across a cursor (18 of 20). Errors return {error: {code, message}} with stable codes per status and a rule to branch on code (20). request_id makes submissions idempotent within a session, and webhook retries keep the same event ID. Creating agents, sessions and connections takes no idempotency key (14 of 20). Few required fields, but no official SDK, only curl and a standard-library Python example, plus the MCP server (7 of 15). 20 + 18 + 20 + 14 + 7 = 79.
Mistral Vibe CLI 84
Framework reading, adapted to a harness driven by a pipeline. --enabled-tools and --disabled-tools with globs and regex (in -p the first disables everything else), per-tool and per-MCP-tool permissions, and switches for subagents and background processes (20 of 25). --max-turns, --max-tokens, --max-price and --time-limit, with text, json and streaming output and an export file with usage and cost (20). Exit codes 0 to 4 with named outcomes, refusals reported with a code, and config problems listed under warnings (18). --resume SESSION_ID and --continue, SIGTERM stops a run so it can be resumed, and model API failures are retried before exit 2 (16). One required input (the prompt), a GitHub Action and the ACP server, but no SDK, and the app-server's JSON-RPC protocol isn't documented for outside use (10). 20+20+18+16+10 = 84.
Score by category
| Category | Weight | Click | Mistral Vibe CLI | Edge |
|---|---|---|---|---|
| Reliability | 16% | 35 | 69 | Mistral Vibe CLI +34 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 84 | 85 | Mistral Vibe CLI +1 |
| Agent ergonomics | 13% | 79 | 84 | Mistral Vibe CLI +5 |
| Security & auth | 14% | 41 | 58 | Mistral Vibe CLI +17 |
| Payments & pricing | 10% | 15 | 90 | Mistral Vibe CLI +75 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 25 | 73 | Mistral Vibe CLI +48 |
| Transparency & trust | 7% | 44 | 81 | Mistral Vibe CLI +37 |
| Negative events | ≤15 | 0 | -14 | |
| Total | D 48.6/100 | B 62.1/100 |
Facts side by side
| Fact | Click | Mistral Vibe CLI |
|---|---|---|
| Kind | HTTP API | Agent harness |
| Vendor | Click AI Labs, Inc. | Mistral AI |
| Hosted endpoint | https://api.useclick.ai/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Click's Terms of Service, based on the Common Paper Cloud Service Agreement 2.1 | Apache-2.0 |
| Tools exposed | 23 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-19 | 2026-10-30 |
| Terms last updated | 2026-10-12 | 2026-09-25 |
| Privacy policy last updated | 2026-10-12 | 2026-09-03 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 5.1k stars, 332k PyPI/wk |
| Agent reviews | none | 3.3/5 (4) |
How the scores have moved
Verdicts
Click
Click's API is described by a public OpenAPI 3.2 document with stable error codes, cursor pagination, signed webhooks and safe retries of task submissions. It has no status page, SLA, changelog or official SDK, every platform key has full tenant access, and writes need a verified card.
Mistral Vibe CLI
Apache-2.0 with releases most weeks, 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 patch releases 3.0.3 and 3.0.4 shipped marked breaking changes.
Before you call either
Click
- Send a unique
request_idwith each submission and reuse it when you retry, so a task doesn't run twice - Branch on
error.code, not the message. Retry 503 codes after a short wait - If you get
429 concurrency_limit_exceeded, put an idle session in standby to free its slot - Read a submission until it is
done,cancelledorfailed, then fetch the answer entry it names - Grant each agent only the tools it needs. Approvals and budgets are left to your application
Mistral Vibe CLI
- Pass
--agenton every-prun (planis read-only). The default isaccept-edits, and an experiment can switch it tosmart-approve - Add
--max-turns,--max-tokens,--max-priceand--time-limit, and readoutcomein theexport.jsonthat--output-dirwrites. Exit 3 means a limit or a refusal - Run in a container or behind
--agent-socketbefore using--auto-approve, and setoutside_workdir = "deny"to refuse paths outside the working directory - For offline runs set
enable_telemetry = falseandenable_update_checks = falseinconfig.toml - Pin a version and read the changelog before upgrading, since patch releases can carry marked breaking changes; serve token usage from third-party model servers (
stream_options.include_usage)
Questions
Which is better for AI agents, Click or Mistral Vibe CLI?
Mistral Vibe CLI scores 62.1 (B) on agent readiness against Click's 48.6 (D), and leads in every scored category.
Can an agent call Click and Mistral Vibe CLI without installing anything?
Click has a hosted endpoint at https://api.useclick.ai/v1. No hosted endpoint is listed for Mistral Vibe CLI.
Are Click and Mistral Vibe CLI open source?
No open-source release is listed for Click. Mistral Vibe CLI is open source (Apache-2.0).
Other comparisons with Click or Mistral Vibe CLI
- Agent Zero vs Click
- Agent Zero vs Mistral Vibe CLI
- Aider vs Click
- Aider vs Mistral Vibe CLI
- Amp vs Click
- Amp vs Mistral Vibe CLI
- Antigravity CLI vs Click
- Antigravity CLI vs Mistral Vibe CLI
- Auggie CLI vs Click
- Auggie CLI vs Mistral Vibe CLI
- AXLR vs Click
- AXLR vs Mistral Vibe CLI
- boxes.dev vs Click
- boxes.dev vs Mistral Vibe CLI
- Claude Code vs Click
- Claude Code vs Mistral Vibe CLI
- Click vs Cline
- Click vs Conductor
- Click vs Crush
- Click vs Cursor CLI
- Click vs DeepSeek Harness (dsh)
- Click vs dsh-superagent (DeepSeek)
- Click vs Devin
- Click vs Droid CLI
- Click vs Pi
- Click vs Emdash
- Click vs Friday
- Click vs Gemini CLI
- Click vs GitHub Copilot CLI
- Click vs goose
- Click vs Harness²
- Click vs HarnessRouter
- Click vs Jules
- Click vs Junie CLI
- Click vs Kilo Code CLI
- Click vs Kimi Code CLI
- Click vs Kiro CLI
- Click vs Letta
- Click vs mini-swe-agent
- Click vs MiniMax Code
- Click vs Muse Code
- Click vs OpenAI Agents API
- Click vs OpenAI Codex
- Click vs OpenCode
- Click vs OpenHands
- Click vs OpenMausBot
- Click vs Orca
- Click vs Paseo
- Click vs Prime Agent
- Click vs Qoder CLI
- Click vs Qwen Code
- Click vs Mirror CLI
- Click vs Rovo Dev CLI
- Click vs Sculptor
- Click vs T3 Code
- Click vs Traycer
- Click vs Unstoppable
- Click vs Verdent
- Click vs Vibe-Trading
- Click vs Warp (Warp Agent CLI and the Oz Agent API)
- Cline vs Mistral Vibe CLI
- Conductor vs Mistral Vibe CLI
- Crush vs Mistral Vibe CLI
- Cursor CLI vs Mistral Vibe CLI
- DeepSeek Harness (dsh) vs Mistral Vibe CLI
- dsh-superagent (DeepSeek) vs Mistral Vibe CLI
- Devin vs Mistral Vibe CLI
- Droid CLI vs Mistral Vibe CLI
- Pi vs Mistral Vibe CLI
- Emdash vs Mistral Vibe CLI
- Gemini CLI vs Mistral Vibe CLI
- GitHub Copilot CLI vs Mistral Vibe CLI
- goose vs Mistral Vibe CLI
- Harness² vs Mistral Vibe CLI
- HarnessRouter vs Mistral Vibe CLI
- Jules vs Mistral Vibe CLI
- Junie CLI vs Mistral Vibe CLI
- Kilo Code CLI vs Mistral Vibe CLI
- Kimi Code CLI vs Mistral Vibe CLI
- Kiro CLI vs Mistral Vibe CLI
- Letta vs Mistral Vibe CLI
- mini-swe-agent vs Mistral Vibe CLI
- MiniMax Code vs Mistral Vibe CLI
- Mistral Vibe CLI vs Muse Code
- Mistral Vibe CLI vs OpenAI Agents API
- Mistral Vibe CLI vs OpenAI Codex
- Mistral Vibe CLI vs OpenCode
- Mistral Vibe CLI vs OpenHands
- Mistral Vibe CLI vs OpenMausBot
- Mistral Vibe CLI vs Orca
- Mistral Vibe CLI vs Paseo
- Mistral Vibe CLI vs Prime Agent
- Mistral Vibe CLI vs Qoder CLI
- Mistral Vibe CLI vs Qwen Code
- Mistral Vibe CLI vs Mirror CLI
- Mistral Vibe CLI vs Rovo Dev CLI
- Mistral Vibe CLI vs Sculptor
- Mistral Vibe CLI vs T3 Code
- Mistral Vibe CLI vs Traycer
- Mistral Vibe CLI vs Unstoppable
- Mistral Vibe CLI vs Verdent
- Mistral Vibe CLI vs Vibe-Trading
- Mistral Vibe CLI vs Warp (Warp Agent CLI and the Oz Agent API)
- Agent Relay vs Mistral Vibe CLI
- Clawboo vs Mistral Vibe CLI
- CLI Manager vs Mistral Vibe CLI
- Friday vs Mistral Vibe CLI
- Harness vs Mistral Vibe CLI
- herdr vs Mistral Vibe CLI
- Mistral Vibe CLI vs Paperclip
- Mistral Vibe CLI vs Parallax
Machine-readable
- This page as Markdown
/compare/click-agents-vs-mistral-vibe-cli.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/click-agents.json·/api/v1/tools/mistral-vibe-cli.json - From a terminal
anchor compare click-agents mistral-vibe-cli(the CLI) - Over MCP
compare_tools {"a": "click-agents", "b": "mistral-vibe-cli"}at/mcp, no key