---
title: "Mistral Vibe CLI | Ethical Stack"
url: https://ethicalstack.ai/harnesses/mistral-vibe/
catalog_version: f6baff2119d0e9158520da7fbe4232011dac79f25bd08757436d7a1dbd593db2
---

# Mistral Vibe CLI

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

Canonical profile: https://ethicalstack.ai/harnesses/mistral-vibe/

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

Published overall: 3.8; 4/6 dimensions rated.

Round the equal-weight mean of available numerical ratings to one decimal; require at least four of six for an overall score. BDS status stays outside the mean; for eligible profiles, a boycott target caps the final score at 2/10 and a pressure target subtracts one point (minimum 1). Not listed and not checked do not adjust the score.

## Energy practices

Finding: 3/10

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#energy

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

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

Argument: 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.

Type: argument; confidence: medium

Scope (dimension): Mistral Vibe CLI client; selected local or remote inference route

Research reviewed: not recorded; evidence date: not recorded

Unknowns: 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.

```json
{
  "method": "practices-transparency-v1",
  "scope": "Mistral Vibe CLI client; selected local or remote inference route",
  "components": {
    "disclosure": {
      "score": 1,
      "reason": "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.",
      "sourceUrls": [
        "https://docs.mistral.ai/vibe",
        "https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli"
      ]
    },
    "electricity": {
      "score": 0,
      "reason": "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.",
      "sourceUrls": [
        "https://docs.mistral.ai/vibe",
        "https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli"
      ]
    },
    "demand": {
      "score": 1,
      "reason": "Vibe supports model choice and agent modes; these select the work and provider but do not establish measured energy savings.",
      "sourceUrls": [
        "https://docs.mistral.ai/vibe",
        "https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli"
      ]
    }
  },
  "actualImpactMeasured": false
}
```

- [Mistral Vibe overview](https://docs.mistral.ai/vibe) (primary; checked 2026-10-24)

- [Install the Vibe CLI and send your first prompt](https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli) (primary; checked 2026-10-24)

## Training data

Finding: Depends on the model

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#training-rights

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

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

Argument: 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.

Type: argument; confidence: medium

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

Research reviewed: not recorded; evidence date: not recorded

Unknowns: Selected model, provider route, corpus provenance, licenses and local-vs-remote handling are installation-specific.

```json
{
  "method": "training-rights-evidence-v1",
  "scope": "The stated training release or selected model",
  "components": null,
  "routeDependency": "The CLI itself does not provide one training corpus; each selected model/provider determines the corpus-rights assessment.",
  "modelReference": null
}
```

- [Mistral Vibe overview](https://docs.mistral.ai/vibe) (primary; checked 2026-10-24)

- [Install the Vibe CLI and send your first prompt](https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli) (primary; checked 2026-10-24)

## Your data & privacy

Finding: Not enough evidence

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#privacy

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

Reason: The client supports multiple model routes with different privacy terms.

Argument: 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.

Type: argument; confidence: low

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

Research reviewed: not recorded; evidence date: not recorded

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

- [Mistral Vibe overview](https://docs.mistral.ai/vibe) (primary; checked 2026-10-24)

- [Mistral AI Products Privacy Policy](https://legal.mistral.ai/terms/privacy-policy/) (primary; checked 2026-10-24)

## Openness

Finding: 7/10

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#openness

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

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

Argument: 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.

Type: argument; confidence: medium

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

Research reviewed: not recorded; evidence date: not recorded

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

- [Mistral Vibe overview](https://docs.mistral.ai/vibe) (primary; checked 2026-10-24)

- [Install the Vibe CLI and send your first prompt](https://docs.mistral.ai/getting-started/quickstarts/vibe-code/install-cli) (primary; checked 2026-10-24)

- [Mistral AI Products Privacy Policy](https://legal.mistral.ai/terms/privacy-policy/) (primary; checked 2026-10-24)

## Worker protections

Finding: 2/10

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#labour

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.

Reason: 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.

Argument: 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. This entry carries the same developer/operator finding to Mistral Vibe CLI; it does not establish that this product was deployed under every cited relationship.

Type: argument; confidence: low

Scope (dimension): Mistral AI: the documented developer/operator record, not proof of deployment of Mistral Vibe CLI.

Research reviewed: 2026-10-24; evidence date: not recorded

Unknowns: 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.

```json
{
  "method": "worker-safeguards-evidence-v1",
  "entity": "mistral",
  "company": "Mistral AI",
  "scope": "Mistral AI's workforce and disclosed contractors. Coverage of individual product teams may be incomplete.",
  "components": {
    "conditions": {
      "score": 1,
      "reason": "A supplier code is a stated business requirement, but its labor content and implementation were not publicly inspectable in this review.",
      "sourceUrls": [
        "https://help.mistral.ai/en/articles/347637-do-you-have-a-code-of-conduct",
        "https://trust.mistral.ai/"
      ]
    },
    "voice": {
      "score": 0,
      "reason": "No public worker-specific voice or grievance mechanism was established in the accessible sources.",
      "sourceUrls": [
        "https://help.mistral.ai/en/articles/347637-do-you-have-a-code-of-conduct",
        "https://trust.mistral.ai/"
      ]
    },
    "assurance": {
      "score": 0,
      "reason": "The Trust Center shows contractor code acknowledgment but no labor-specific audits, remediation or outcomes.",
      "sourceUrls": [
        "https://help.mistral.ai/en/articles/347637-do-you-have-a-code-of-conduct",
        "https://trust.mistral.ai/"
      ]
    }
  },
  "disclosureLimited": true,
  "meaning": "This grades documented worker safeguards, not a measured rate of mistreatment."
}
```

- [Do you have a Code of Conduct?](https://help.mistral.ai/en/articles/347637-do-you-have-a-code-of-conduct) (primary; checked 2026-10-24)

- [Mistral AI Trust Center](https://trust.mistral.ai/) (primary; checked 2026-10-24)

## Military ties

Finding: 3/10

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#military-contracts

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.

Reason: 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.

Argument: 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. This entry carries the same developer/operator finding to Mistral Vibe CLI; it does not establish that this product was deployed under every cited relationship.

Type: argument; confidence: medium

Scope (dimension): Mistral AI: the documented developer/operator record, not proof of deployment of Mistral Vibe CLI.

Research reviewed: 2026-10-24; evidence date: 2026-10-24

Unknowns: The sources do not establish 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.

```json
{
  "method": "military-ties-priority-v2",
  "entity": "mistral",
  "company": "Mistral AI",
  "scope": "Mistral AI's relationships and safeguards. A company relationship does not identify every product or release used.",
  "components": {
    "restrictions": {
      "score": 0,
      "reason": "The reviewed public partnership and company materials do not disclose binding restrictions on weapons, harmful surveillance, or military-intelligence use.",
      "sourceUrls": [
        "https://helsing.ai/newsroom/helsing-and-mistral-announce-strategic-partnership-in-defence-ai",
        "https://mistral.ai/about/"
      ]
    },
    "oversight": {
      "score": 0,
      "reason": "No public military-specific review, enforcement mechanism, or independent outcome assessment was identified in the reviewed partnership materials.",
      "sourceUrls": [
        "https://helsing.ai/newsroom/helsing-and-mistral-announce-strategic-partnership-in-defence-ai",
        "https://mistral.ai/about/"
      ]
    },
    "transparency": {
      "score": 2,
      "reason": "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.",
      "sourceUrls": [
        "https://helsing.ai/newsroom/helsing-and-mistral-announce-strategic-partnership-in-defence-ai",
        "https://www.airbus.com/en/newsroom/press-releases/2026-05-airbus-partners-with-mistral-ai-to-strengthen-the-use-of-artificial-intelligence-in-sovereign"
      ]
    }
  },
  "relationship": "broad-defense",
  "relationshipReason": "Mistral publicly confirms joint defense-AI development and military-aerospace partnerships, but no source establishes its model in actual targeting or combat intelligence use.",
  "score": 3,
  "baseScore": 1,
  "safeguardPoints": 2,
  "safeguardAdjustment": 2,
  "rawScore": 3,
  "cap": 3,
  "disclosureLimited": true,
  "meaning": "Known military relationships take priority over missing safeguards. The rating does not establish the probability of an undisclosed contract."
}
```

- [Helsing and Mistral announce strategic partnership in defence AI](https://helsing.ai/newsroom/helsing-and-mistral-announce-strategic-partnership-in-defence-ai) (primary; checked 2026-10-24)

- [About Mistral](https://mistral.ai/about/) (primary; checked 2026-10-24)

- [Airbus and Mistral AI partner for AI in aerospace](https://www.airbus.com/en/newsroom/press-releases/2026-05-airbus-partners-with-mistral-ai-to-strengthen-the-use-of-artificial-intelligence-in-sovereign) (primary; checked 2026-10-24)

## BDS targets

Finding: Not listed

Assessment: https://ethicalstack.ai/harnesses/mistral-vibe/#israel-palestine

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

Reason: 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.

Argument: 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. This entry carries the same developer/operator finding to Mistral Vibe CLI; it does not establish that this product was deployed under every cited relationship.

Type: conditional; confidence: medium

Scope (dimension): Mistral AI: the documented developer/operator record, not proof of deployment of Mistral Vibe CLI.

Research reviewed: not recorded; evidence date: not recorded

Unknowns: 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.

- [BNC target list (not checked for this company)](https://bdsmovement.net/Guide-to-BDS-Boycott) (campaign; checked 2026-10-24)

- [BNC target list (not checked for this company)](https://bdsmovement.net/no-tech-oppression-apartheid-or-genocide) (campaign; checked 2026-10-24)

## Reading the evidence

- Assessments are provisional editorial judgments. Cite the profile and the underlying sources, and retain confidence, scope and unknowns.

- Unknown, not-applicable and model-dependent are different states. Missing evidence does not establish good or bad conduct.

- Company-level evidence does not establish use of a particular product or model. Account plan, model, host and route can change an assessment.

- Energy scores describe documented practices and transparency, not measured request emissions. Zero component points can mean an evidence gap.

- Published overall scores require at least four of six numerical dimensions. Preserve coverage and BDS adjustments; BDS itself is categorical.

- No named BDS target found is limited to the reviewed campaign sources and is not approval. Personalized priorities do not change the published overall score.

- Review and source-check dates describe the research, not this deployment. Fetch current primary sources when the decision requires current verification.

Methodology: https://ethicalstack.ai/methodology/