Ethical Stack.

Mistral Vibe CLI

Terminal coding agent for local repositories, with optional Mistral-hosted or compatible model routes.

Score calculation

(3 + 7 + 2 + 3) ÷ 4 = 3.8

4 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Vibe CLI on the user’s machine; prompt processing follows the model provider and account route configured by the user.

What fits your needs

Vibe CLI on the user’s machine; prompt processing follows the model provider and account route configured by the user.

Where it fits

Use Vibe in a terminal for codebase work, or direct it to a local model or compatible API.

See the evidence
Tradeoffs to expect

Route and limits

Local repository access and shell use depend on the active agent approval mode; remote inference still sends prompt context to its provider.

See the evidence
How to switch

Try it

Install the Vibe CLI, select a provider, then test it in a non-sensitive project directory.

See the evidence
Practical questions

Before relying on it

Review provider/model configuration, local folder trust, agent approval mode, and conversation persistence.

See the evidence

Energy practices

3/10↑

Public docs establish the Mistral Vibe CLI client; selected local or remote inference route route; they don’t show its request-level physical footprint. Vibe supports model choice and agent modes; these select the work and provider but don’t confirm measured energy savings.

See the evidence

This practices and disclosure grade covers Mistral Vibe CLI client; selected local or remote inference route. Public product/API documentation establishes how this route operates and the listed user controls, but gives no measured per-request energy, emissions or water. A corporate electricity claim is not allocated to this route.

1 + 1 reporting + 0 electricity + 1 controls = 3/10. This grades documented practices and transparency.

Request-level electricity, emissions, water use, serving utilization and any route-specific clean-power matching are not reported for Mistral Vibe CLI client; selected local or remote inference route.

Reporting1/3
Official documentation describes the Mistral Vibe CLI client; selected local or remote inference route operating boundary, but does not publish a dated quantitative energy, emissions or water result for this route.
Electricity sourcing0/3
The reviewed sources do not map Mistral Vibe CLI client; selected local or remote inference route to a site-specific electricity mix or time-matched clean-power supply.
Resource controls1/3
Vibe supports model choice and agent modes; these select the work and provider but don’t confirm measured energy savings.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

The CLI itself does not provide one training dataset; each selected model/provider determines the training-data rights assessment.

See the evidence

Vibe is a coding client, not a single trained model. Its documentation supports Mistral, local and compatible-provider routes, so training-data provenance and permissions must be evaluated for the selected model instead of inferred from the client.

Selected model, provider route, training data provenance, licenses and local-vs-remote handling are installation-specific.

Your data & privacy

—Not enough evidence↑

The CLI can use Mistral accounts, API keys, local models, or compatible third-party providers; prompt retention depends on the chosen route.

See the evidence

Mistral Vibe CLI runs locally and supports either Mistral-hosted models or local/OpenAI-compatible providers. Mistral’s product policy gives retention rules for Mistral routes, but cannot determine the handling of all alternate providers configured in the CLI; therefore no route-independent privacy score is assigned.

Selected provider and model, API route, local config, conversation persistence and provider-specific retention must be checked for each installation.

Openness

7/10↑

A locally installable CLI that can use local models or API-compatible providers; the inference backend remains configurable.

See the evidence

Mistral’s CLI installation guide documents a local Python package and explicitly supports offline local models or OpenAI-compatible API keys. This provides local client control, though provider routes and model licenses remain separate.

Locally installed client with local-model and compatible-provider support.

The configured API or local model has its own runtime, license, data retention and safety behavior.

Worker protections

2/10↑

Mistral publicly says its supplier code applies to goods and services and its Trust Center shows contractors acknowledge a code, but labor-specific provisions and outcomes were not publicly inspectable.

See the evidence

Mistral’s August 2026 help page states that its Code of Conduct sets standards suppliers are expected to follow for Mistral business and all supplier goods/services; the Trust Center lists contractor acknowledgment of the Code of Conduct. The public interface did not expose the code’s labor clauses or worker procedures, and no worker survey, audit, pay/conditions disclosure or remediation results were located. This supports limited credit for a supplier-code commitment only. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 1 pay & conditions + 0 worker voice & remedy + 0 evidence & follow-through = 2/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The supplier code’s detailed labor language and coverage of AI data workers, grievance route, monitoring and outcomes were not accessible from the public Trust Center.

Pay & conditions1/3
A supplier code is a stated business requirement, but its labor content and implementation were not publicly inspectable in this review.
Worker voice & remedy0/3
No public worker-specific voice or grievance mechanism was established in the accessible sources.
Evidence & follow-through0/3
The Trust Center shows contractor code acknowledgment but no labor-specific audits, remediation or outcomes.
Workers rubric ↗

Military ties

3/10Broad defense ties↑

Mistral AI publicly partners with defense AI company Helsing on joint development of vision-language-action models, and its current company page says it serves defense customers. A separate Airbus agreement includes military aerospace applications; specific Mistral model deployments in weapons systems are not established.

See the evidence

Mistral's announcement with Helsing describes joint development of next-generation AI systems for European defense, while Helsing's announcement links its military AI portfolio to Ukraine-deployed strike drones and fighter electronic-warfare capabilities. Mistral also identifies defense as a customer sector and Airbus says the partnership includes military aerospace applications. This is broad defense enablement, capped at 3/10; no binding weapons/surveillance prohibitions or military-use oversight outcomes are public in these sources. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 0 use restrictions + 0 enforcement & oversight + 2 relationship disclosure = 3/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.

The sources don’t confirm which Mistral models, if any, are deployed in specific military systems, the operational purpose or safeguards, contract restrictions, or independent oversight. Helsing's existing strike systems are not evidence that Mistral models themselves control or target weapons.

Use restrictions0/4
The reviewed public partnership and company materials do not disclose binding restrictions on weapons, harmful surveillance, or military-intelligence use.
Enforcement & oversight0/3
No public military-specific review, enforcement mechanism, or independent outcome assessment was identified in the reviewed partnership materials.
Relationship disclosure2/2
Mistral and its partners identify the defense relationships and intended applications, including VLA model development and military aerospace, though no model-level deployment details or outcomes are disclosed.

Mistral publicly confirms joint defense-AI development and military-aerospace partnerships, but no source establishes its model in actual targeting or combat intelligence use. The relationship limits this grade to 3/10.

Military rubric ↗

BDS targets

Not listed↑

No named target found in the two checked BNC campaign lists.

See the evidence

Company name checked against the BNC consumer boycott/pressure guide and official No Tech campaign list; no named target found. This limited list check is not BDS approval and does not cover every campaign, subsidiary, supplier, or product route. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

Company name checked against the BNC consumer boycott/pressure guide and official No Tech campaign list; no named target found. This limited list check is not BDS approval and does not cover every campaign, subsidiary, supplier, or product route.

More from Mistral AI

All sources

Side by side