HarnessMatch

Search 73 product records by name, workflow, interface, or documented capability.

Quick access
Use ↑ ↓ to move, Enter to open, Esc to close.

Quick access links shown.

Menu

Coding agent

Mistral Vibe

Open multi-provider CLI and IDE agent with permissions, delegation, and rewind.

Status
Active
License
Apache-2.0
Evidence
Documented + code-verifiable, 31 sources
Product record checked
2026-08-22
Compare harnessesInspect sources

At a glance

Mistral's Apache-2.0 coding harness combines an interactive CLI and ACP editor integration with local or hosted models, delegated subagents, MCP, skills, policy hooks, structured automation, durable sessions, and message-level file rewind.

Good choice if

  • Vibe coders who want approvals, a plan mode, and file rewind without giving up a capable agent
  • Mistral-plan users or teams that want an open, inspectable terminal and ACP editor agent
  • Developers running local or OpenAI-compatible models through a configurable provider layer
  • Automated runs with turn, token, and price budgets plus structured output
  • Teams enforcing policy through per-tool permissions and inherited lifecycle hooks

Check before choosing

  • The local CLI executes on the host: permissions and Git worktrees are controls, not an OS sandbox; Vibe Code Web's managed sandbox is a separate surface
  • Anonymous telemetry, update checks, and auto-update are enabled by default; a fully offline setup requires disabling them and any networked tools
  • The source audit remains pinned to v2.22.0; v2.23.x release notes document new MCP commands, a JSON-RPC app-server refactor, and a standalone app-server binary, but those newer implementation changes remain release-level evidence until a fresh source audit
See 2 more considerations
  • Version 2.24.1 renames the default agent to `ask` but gives it an `accept-edits` default, so the name alone must not be interpreted as per-action approval
  • There is no built-in browser automation; web search and fetch tools are not a browser agent

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-28The source establishes the mechanism, not its quality or availability in every mode.
Reusable skills
DocumentedProduct-supported reusable skill packagesSource · checked 2026-07-28Support does not establish portability, package quality, safety, or adoption.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-28The source establishes the mechanism, not its quality or availability in every mode.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-28The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-28The source establishes the mechanism, not its quality or availability in every mode.
Browser control
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Undo file changes
DocumentedProduct-supported file or session rollbackSource · checked 2026-07-28The source establishes the mechanism, not its quality or availability in every mode.

Getting started

Install `mistral-vibe`, use a Mistral plan or API key, or configure a local/OpenAI-compatible provider. Then review the default `ask` agent's accept-edits posture before running `vibe`.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced

  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

    EvidenceVibe overview

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

    EvidenceWork with the CLI

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

    EvidencePinned local-session architecture

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

    EvidenceSafety, approvals, and permissions

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationWorkspace isolationDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible toolsDocumented mechanism, not a performance score.
  • Context & stateManaged contextDocumented mechanism, not a performance score.
  • Lifecycle & recoveryCheckpoint/rewindDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsPolicy controlsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

3/5public artifacts present
Security policy
Not found
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The v2.22.0 tree contains 387 Python test files and CI but no repository security policy or dedicated evaluation suite. Product docs still contradict shipped code on programmatic approval defaults and MCP OAuth; no product benchmark is inferred from engineering tests.

Inspect commit 89350a4064ca90e4732271dcc27688e5d684871d, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs
Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage
  • Latest stable releasev2.25.0Released 2026-09-04; 26 stable releases in 90 daysOpen release
  • Homebrew 30d events1.1KFormula: mistral-vibeOpen artifact
  • Release asset downloads267.84K83 stable releases; 619 matched assetsOpen artifact
  • VS Code installs32.15KExtension: mistralai.mistral-vibe-codeOpen artifact
  • Open VSX downloads15.75KExtension: mistralai/mistral-vibe-code; latest 1.20.0Open artifact
  • GitHub stars4.93KFull-source repository; 691 forksOpen artifact

Routing, package retrievals, release downloads, editor installs, and repository interest observe different populations. They are never added together and never affect capability evidence, classification, or measured results.

Interpretation rulesSignals checked

First-party evidence

Each capability claim links to the first-party record that supports it.

31 first-party sourcesProduct record checked

Execution and control

1 source

Agents, state and recovery

2 sources
View 1 more source

Releases and public code audit

2 sources
View 1 more source

Additional first-party sources

26 sources
View 25 more sources

Ecosystem context

CLIArena Mistral Vibe adapters and Terminal-Bench runs Independent, inspectable discovery signal only. Reported Terminal-Bench 2.0 runs use a modified Mistral Vibe fork and do not yet meet HarnessMatch's full immutable configuration and replication requirements, so no score is imported. Observed 2026-07-28.