Head to head · Agent harnesses · October 2026 research run

Mistral Vibe CLI vs Sculptor

Mistral Vibe CLI scores 58.4 (C) on agent readiness against Sculptor's 53.1 (D), and leads in 5 of 7 scored categories. Both do agent harnesses.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Which one, for what

Mistral Vibe CLI C

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 43
  • Schema & documentation, 85 against 45
  • Agent ergonomics, 84 against 50
  • Transparency & trust, 81 against 57

Also in its favour

  • Free to start without a card

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

Sculptor D

Best for Developers who want parallel coding agents in isolated workspaces and are fine with a research preview.

Also in its favour

  • No key needed to call it
  • No incidents deducted, where Mistral Vibe CLI loses 14 points for them

Watch for

Labelled an experimental research preview that may change drastically

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.

Schema & documentation Mistral Vibe CLI +40

Mistral Vibe CLI 85

Framework reading. A configuration reference with each key's type and default, the export.json fields, and the --agent-socket JSON-RPC methods with typed params and results in the README, plus ACP. Since 3.0.3 vibe config schema prints a JSON schema of every setting, including each built-in tool's; the streaming events still have no published schema (20 of 25). docs.mistral.ai/llms.txt indexes the CLI pages, each with a Markdown twin (10). The safety page says what each agent allows and when to use it, and on 2 November it agrees with the source. -p runs the configured default_agent and denies calls that need approval, and the offline guide and configuration reference name enable_update_checks. The 18 October contradictions and TODO notes are gone (15 of 20). Output formats, agent names, permission values and OpenTelemetry redaction modes are enums, and the config is validated on load (12). Many examples and an exit-code table that maps each code to the outcome names in export.json (13). Dated changelog and version tags (15). 20+10+15+12+13+15 = 85.

Sculptor 45

Harness reading. A README, specs and agent docs in the repository; no API reference (45).

Agent ergonomics Mistral Vibe CLI +34

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.

Sculptor 50

Harness reading. Workspaces as isolated copies, review and merge back, and built-in skills (50).

Reliability Mistral Vibe CLI +26

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.

Sculptor 43

Local software. Desktop downloads for Mac (Apple Silicon), Linux and Linux ARM64 (20). checks.yml and a PR gate run on the repository; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). sculptor-v tags up to v0.49.0, no changelog file (8). 0.x and labelled a research preview (0). 20 + 15 + 0 + 8 + 0 = 43.

Transparency & trust Mistral Vibe CLI +24

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.

Sculptor 57

MIT (30). Consent-based telemetry documented in the repository (18 of 30). The README warns of drastic changes during the research preview, with no deprecation policy (5). Opt-in telemetry (20). 30 + 18 + 5 + 20 = 73.

Score by category

CategoryWeight this runMistral Vibe CLISculptorEdge
Reliability16%206943Mistral Vibe CLI +26
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28545Mistral Vibe CLI +40
Agent ergonomics13%16.28450Mistral Vibe CLI +34
Security & auth14%17.55857Mistral Vibe CLI +1
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87375Sculptor +2
Transparency & trust7%8.88157Mistral Vibe CLI +24
Negative events≤15-140
TotalC 58.4/100D 53.1/100

Facts side by side

FactMistral Vibe CLISculptor
KindAgent harnessAgent harness
VendorMistral AIImbue, Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentedyesno
llms.txtyesno
Last release2026-10-302026-11-06
Terms last updated2026-09-25no document linked
Privacy policy last updated2026-09-03no document linked
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity5.1k stars, 332k PyPI/wknone
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

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.

Sculptor

Imbue's open-source app for parallel coding agents in isolated workspaces, with telemetry off until you choose otherwise. It's an experimental research preview that warns of bugs and drastic changes, Mac and Linux only, with no changelog.

Before you call either

Mistral Vibe CLI

  1. Pass --agent on every -p run (plan is read-only). The default is accept-edits, 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, and set outside_workdir = "deny" to refuse paths outside the working directory
  4. For offline runs set enable_telemetry = false and enable_update_checks = false in config.toml
  5. 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)

Sculptor

  1. Download from the README's links, connect a repository and create a workspace before prompting
  2. Review the diff before merging a workspace back to main

Questions

Which is better for AI agents, Mistral Vibe CLI or Sculptor?

Mistral Vibe CLI scores 58.4 (C) on agent readiness against Sculptor's 53.1 (D), and leads in 5 of 7 scored categories.

Are Mistral Vibe CLI and Sculptor open source?

Yes. Mistral Vibe CLI is open source (Apache-2.0). Sculptor is open source (MIT).

Other comparisons with Mistral Vibe CLI or Sculptor

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.