Skip to main content
Mistral Vibe SignalsBack to the read

Every source behind the read

Every source GILD analyzed, newest first. Each says who the source is, how it knows, whether it still applies and which findings it counts toward. Open a count to see only its sources.

Whose sources count

Source

85 sources in All practitioners, with product documentation Showing all 85 sources

  1. Mixed

    maelito, Hacker News commenter

    Comment on: Timestral: Mistral's time-series foundation modelsHacker News comment

    Mistral Large 4 worked well in Vibe but was far too slow, so maelito switched back to GLM-5.3, called awesome, then found it slow too under load.

    Published Oct 19, 2026self-described: Tested Mistral Large 4 in Vibe

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on Mistral 4
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-19, Mistral 4
    Counts toward
    Reliability, service availability: unfavorable, G1 (1 unit before bounds)
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Vibe with Mistral Large 4 and GLM-5.3

  2. Mixed

    nozzlegear, developer using a Vibe subscription through OMP

    Comment on: Mistral models through a Vibe subscriptionHacker News comment

    Reports slow responses from Mistral 4 and the hosted GLM offering while using OMP with a Vibe subscription in the US.

    Published Oct 19, 2026self-described: Mistral 4 and GLM accessed through OMP with a Vibe subscription

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Observed on Mistral 4
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-19, Mistral 4
    Counts toward
    Reliability, service availability: unfavorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  3. Positive

    data-ottawa, developer using Mistral Vibe

    Comment on: Mistral Vibe and Mistral 4Hacker News comment

    After pointing Vibe at Mistral 4, the developer found usage charged against subscription capacity, with no separate API allowance.

    Published Oct 19, 2026self-described: Mistral Vibe configured for Mistral 4

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Observed on Mistral 4; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-19, Mistral 4
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Cost predictability and limits, cost transparency: repeats a stronger account in its group
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  4. Negative

    themflyingjaffacakes, Reddit r/MistralAI poster

    tried Vibe CLI for the first time. What a hot mess.Reddit post

    On first use the model ignored instructions and priorities, and 15 minutes of asking Vibe to stop requesting permissions never stuck across sessions.

    Published Oct 8, 2026self-described: Long-term supporter of EU AI; uses the Mistral API for privacy-related calls

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-08
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Operational control, execution control: unfavorable, G2 (2 units before bounds)
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current

  5. Mixed

    phillc73, Hacker News commenter

    Comment on: Mistral Large 4Hacker News comment

    GLM-5.3 powered through a lot of work, but phillc73 used up two subscriptions in six days. Plans cannot be stacked on one account and pay-as-you-go adds up fast, so the extra money went elsewhere.

    Published Oct 6, 2026self-described: Heavy user on two Vibe subscriptions

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on GLM-5.3
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-06, GLM-5.3
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)
    Counts toward
    Cost predictability and limits, limits in practice: unfavorable, G2 (2 units before bounds)
    Not counted
    Cost predictability and limits, cost transparency: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Vibe CLI with GLM-5.3

  6. Positive

    Altruistic_Panda_420, Reddit r/MistralAI poster

    Mistral Vibe Code CLI is GREAT!Reddit post

    Running the same DeepSeek model in many harnesses, Altruistic_Panda_420 rates Vibe the best. It stays in its directory, reads only what it needs, and hits the cache so the test budget lasts longer.

    Published Oct 1, 2026self-described: Has used Pi, Claude Code, Antigravity, Codex, and others on the DeepSeek API

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on deepseek api
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-10-01, deepseek api
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Delivered outcomes, context handling: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Cost predictability and limits, limits in practice: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Operational control, execution control: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Vibe CLI with the DeepSeek API

  7. Mixed

    Maxime Rossi Bellom and Ramtine Tofighi Shirazi, security researchers at SecMate

    Mistral Vibe Shell Permission Bypass Leading to Arbitrary Code ExecutionSecurity research blog

    SecMate showed that Vibe 2.25.0 approved a reduced reading of a shell command and then ran the full string. Commands judged read-only could execute code without a prompt. Mistral fixed it in 2.25.4.

    Published Sep 23, 2026self-described: Security review of Vibe 2.25.0

    Practitioner account, self-described; structured test; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Self-described; Ran a structured test; Artifact checked (log); Observed on Mistral Vibe 2.25.0
    Role
    Name self-described; employer unknown; role unknown
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Ran a structured test
    Support
    1 artifact (log)
    Date and version
    2026-09-23, Mistral Vibe 2.25.0
    Counts toward
    Operational control, execution control: unfavorable, G2 (2 units before bounds), capped: C-relationship

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Engineering Blogs & Studies
    Who
    Professional team
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 2.25.0; fixed in 2.25.4

  8. Mixed

    ublistening, Reddit r/MistralAI poster

    GLM is the most interesting Mistral Vibe development. But is Vibe Pro competitive enough?Reddit post

    ublistening values Mistral's European, privacy-minded approach and calls hosted GLM the most interesting Vibe development, but will not pay for the story alone against Claude, ChatGPT, or Cursor plans.

    Published Sep 23, 2026self-described: Pays for several AI tools and weighs Vibe Pro against them

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Opinion
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-23
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Current
    Observed on
    Vibe with GLM-5.2 and GLM-5.3

  9. Mixed

    RedditPolux, Reddit r/MistralAI poster

    Today, Vibe doesn't care about "plan mode"Reddit post

    After a long session one Vibe client ignored plan mode and edited a file RedditPolux was only planning to change.

    Published Sep 23, 2026self-described: Vibe on two machines and projects with GLM-5.3

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on GLM5.3
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-23, GLM5.3
    Counts toward
    Operational control, execution control: unfavorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 2.x plan agent with GLM-5.3

  10. Mixed

    Difficult-Sugar-4862, Reddit r/MistralAI poster

    Four things I got wrong about Vibe CLI's permission config (2.25.5)Reddit post

    Reading the 2.25.5 source, Difficult-Sugar-4862 found four permission rules that behave differently than they read, such as a short bash allowlist silently dropping the 44 defaults.

    Published Sep 22, 2026self-described: Scopes agents with .vibe/agents permission profiles

    Practitioner account, pseudonymous; structured test; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Specific details; Observed on 2.25.5
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-22, 2.25.5
    Counts toward
    Operational control, execution control: unfavorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 2.25.5

  11. Mixed

    Martypx00, Reddit r/MistralAI poster

    New "unified harness" is unified in ignoring my agent configsReddit post

    After the unified harness update, Vibe ignored Martypx00's custom agent definitions and subagents went searching the .vibe folder for them.

    Published Sep 21, 2026self-described: Uses custom agents and subagents in the Vibe CLI

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-21
    Counts toward
    Reliability, regressions: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck

  12. Mixed

    Simon-LM, Vibe user filing a GitHub issue

    GitHub issue #1113: Unified Harness ignores allowlist on file toolsGitHub issue

    Under the unified harness, an agent profile with a write allowlist could write nothing, and twenty runs ended silently with no file and no error.

    Published Sep 18, 2026self-described: Agent profiles with write allowlists

    Practitioner account, pseudonymous; structured test; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Specific details; Observed on mistral-vibe 2.25.4
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-18, mistral-vibe 2.25.4
    Counts toward
    Operational control, execution control: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck

  13. Negative

    Altrollique, Reddit r/MistralAI poster and regular Claude user

    Using Mistral for code at workReddit post

    Vibe with GLM-5.2 wrote off-point code that ignored the project's style, where Claude matches how the team works; Altrollique wants a European option but cannot trade away quality at work.

    Published Sep 18, 2026self-described: Coding at work; tried Vibe with GLM-5.2 over the summer

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on GLM5.2
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-18, GLM5.2
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with GLM-5.2

  14. Negative

    infinitescript, Reddit r/MistralAI poster on Pro

    Long rant about the stupidity that is Mistral billing. I want to understand the logic.Reddit post

    infinitescript used up a new Pro plan in under an hour. Support explained the budget is shared with Studio and the API and the discounted rate applies only with a Vibe key, which they found confusing.

    Published Sep 18, 2026self-described: Signed up for Pro to use Vibe

    Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Artifact checked (vendor reply); Observed on Pro
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    1 artifact (vendor reply)
    Date and version
    2026-09-18, Pro
    Counts toward
    Cost predictability and limits, cost transparency: unfavorable, G3 (3 units before bounds)
    Not counted
    Cost predictability and limits, cost predictability: repeats a stronger account in its group
    Not counted
    Cost predictability and limits, limits in practice: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  15. No opinion stated

    West_Passion_1665, Reddit r/MistralAI poster

    Regional inferenceReddit post

    Says Mistral's regional inference option "seems like a good solution" for keeping data in the EU but is only available for the API. Uses Vibe CLI, which by default uses the global endpoint, and asks how to configure it to always use the EU endpoint.

    Published Sep 18, 2026self-described: Vibe CLI user who wants all data kept in the EU

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-18
    Counts toward
    Operational control, data control: unfavorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  16. Negative

    lucid_supernova, Reddit r/MistralAI poster

    Mistral doesn't give us sovereignty, or respect our privacy!Reddit post

    The Vibe CLI turns on telemetry and adds a commit signature by default without asking, and Mistral's web app loads US trackers, which undercut the privacy reason lucid_supernova switched.

    Published Sep 16, 2026self-described: Switched to Mistral for privacy

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (issue)
    Date and version
    2026-09-16
    Counts toward
    Operational control, data control: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  17. Negative

    MrViking2k19, Reddit r/MistralAI poster

    I probed all 46 models exposed to my Mistral Free account - even the Vibe CLI models have a 0 RPM limitReddit post

    On a Free account Vibe defaulted to Mistral Medium 3.5, which returned HTTP 429 because its limit was zero requests per minute, and nothing showed which models the tier could use.

    Published Sep 10, 2026self-described: Trying Vibe 2.25.1 on a Free account

    Practitioner account, pseudonymous; structured test; counts toward Operational control, Cost predictability and limits, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Artifact checked (log); Observed on Mistral Vibe v2.25.1
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    2 artifacts (log)
    Date and version
    2026-09-10, Mistral Vibe v2.25.1
    Counts toward
    Cost predictability and limits, cost transparency: unfavorable, G3 (3 units before bounds)
    Counts toward
    Adoption and upkeep, setup: unfavorable, G3 (3 units before bounds)
    Counts toward
    Operational control, models and deployment: unfavorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 2.25.1 on the Free plan

  18. Positive

    maxhille, Hacker News commenter

    Comment on: Mistral Vibe Code: GLM 5.2 is now availableHacker News comment

    About to cancel Pro, maxhille kept it after Vibe started serving GLM-5.2 with an 800k context, a large included quota, and a fast model.

    Published Sep 4, 2026self-described: Pro subscriber who also runs a local Qwen model

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Observed on GLM-5.2; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-04, GLM-5.2
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Cost predictability and limits, limits in practice: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe CLI with GLM-5.2

  19. Positive

    jnurmine, Hacker News commenter

    Comment on: Can I opt out of my input or output data being used for training?Hacker News comment

    For the work jnurmine does, Claude in Kiro and Mistral Vibe are hard to tell apart.

    Published Sep 2, 2026self-described: Uses Claude in Kiro and Mistral Vibe

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-02
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  20. Positive

    evanjrowley, Hacker News commenter

    Comment on: Can I opt out of my input or output data being used for training?Hacker News comment

    Planning with Mistral-hosted GLM-5.2 and implementing through a Vibe key works well, but at the basic plan tier Vibe shares data with Mistral. The user evanjrowley therefore keeps high-level planning on Studio with training off.

    Published Sep 2, 2026self-described: Plans with GLM-5.2 through Mistral Studio and implements with a Vibe key on a basic plan

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on GLM-5.2
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-02, GLM-5.2
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Operational control, data control: mixed, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    GLM-5.2 hosted by Mistral

  21. Negative

    teekert, Team-plan administrator discussing organization-wide data controls

    Comment on: Mistral Vibe Team plan defaultsHacker News comment

    The administrator says Team users should not have to ask each person to disable model-training sharing before company work begins.

    Published Sep 2, 2026self-described: Mistral Vibe Team plan organization settings

    Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Opinion; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-02
    Not counted
    Operational control, data control: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Professional team
    Evidence
    Reported
    Applies to
    Still applicable

  22. Negative

    teekert, Team-plan administrator discussing organization-wide data controls

    Comment on: Mistral Vibe Team plan training defaultHacker News comment

    The Team plan's admin settings moved the interaction-training control to an individual setting, leaving no organization-wide toggle for an administrator.

    Published Sep 2, 2026self-described: Mistral Vibe Team plan organization settings

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Specific details; Observed on Team plan
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-09-02, Team plan
    Counts toward
    Operational control, admin control: unfavorable, G2 (2 units before bounds)
    Counts toward
    Operational control, data control: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Professional team
    Evidence
    Reported
    Applies to
    Still applicable

  23. Mixed

    therealcoiffeur, security researcher filing a GitHub issue

    GitHub issue #997: Remote Code Execution via worktree creation (git attribute filter execution)GitHub issue

    A crafted .gitattributes filter runs arbitrary commands when Vibe creates a worktree, without user action and despite disabled Git hooks.

    Published Aug 12, 2026self-described: A working exploit against the --worktree flag

    Practitioner account, pseudonymous; structured test; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Specific details; Observed on mistral-vibe v2.24.1
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    1 artifact (screenshot)
    Date and version
    2026-08-12, mistral-vibe v2.24.1
    Counts toward
    Operational control, execution control: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  24. Mixed

    Guilty-Pride6761, Reddit r/MistralAI poster on Pro

    Why do Vibe CLI and Vibe VS Code Extension perform so differently? (PRO subscription)Reddit post

    The VS Code extension ran in circles on an ffmpeg error, while the Vibe CLI ran for about 30 minutes, tripped on its own exception handling, and still reached a working solution.

    Published Aug 2, 2026self-described: Python audio processing script

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on PRO subscription
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-08-02, PRO subscription
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds)
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  25. Mixed

    kodmasin, Reddit r/MistralAI poster

    vibe-cli, offline models (ollama), don't preserve context history between messagesReddit post

    With offline models served by Ollama, Vibe did not keep conversation history between messages for kodmasin.

    Published Jul 28, 2026self-described: Vibe CLI with offline models through Ollama

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-07-28
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  26. Mixed

    tom4112, Reddit r/MistralAI poster

    Vibe CLI unusable tonightReddit post

    For one evening the Vibe CLI hallucinated garbled tool names or stuck in endless thinking loops.

    Published Jul 20, 2026self-described: Regular Vibe CLI user

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-07-20
    Counts toward
    Reliability, service availability: unfavorable, G2 (2 units before bounds)
    Not counted
    Reliability, run stability: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  27. Mixed

    bunaventure, Reddit r/MistralAI poster and paying subscriber

    Mistral CLI, what's with the Git commit signatures?Reddit post

    Vibe kept adding its signature to Git commits with include_commit_signature set to false, so bunaventure stopped letting it commit.

    Published Jul 4, 2026self-described: Uses the Vibe CLI with Git

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Artifact checked (transcript)
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (transcript)
    Date and version
    2026-07-04
    Counts toward
    Operational control, execution control: unfavorable, G3 (3 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  28. Negative

    SkyPL, Reddit r/MistralAI poster

    A story of how Mistral Vibe CLI failed to install MCPReddit post

    Spent 30 minutes with Mistral Medium 3.5 in Vibe v2.18.4 on Windows failing to install a locally cloned MCP server; Claude Code then one-shotted it in 3m 37s. Blames the model as "too dumb", plus a Vibe skill with no local-MCP example and no built-in feedback feature.

    Published Jul 2, 2026self-described: Testing several agent harnesses on Windows

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on Mistral Vibe v2.18.4 · mistral-medium-3.5[high], on Windows
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-07-02, Mistral Vibe v2.18.4 · mistral-medium-3.5[high], on Windows
    Counts toward
    Delivered outcomes, task completion: unfavorable, G2 (2 units before bounds)
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 2.18.4 with Mistral Medium 3.5

  29. Positive

    adev_, Hacker News commenter

    Comment on: Leanstral 1.5Hacker News comment

    adev_ uses Mistral mainly through the Vibe CLI because it costs about an order of magnitude less than Claude. It still does the job well on small tasks, prototypes, and refactors. Moves to Claude only when unsatisfied.

    Published Jun 30, 2026self-described: C++ and Python work, with Claude as a fallback

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-30
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  30. Negative

    InsideMikesWorld, Reddit r/MistralAI poster

    Constantly getting stuck in thinking and hitting PoolTimeout error while codingReddit post

    Vibe took ages before any file change and often stalled in thinking until a PoolTimeout error on anything beyond a simple edit, which keeps InsideMikesWorld from relying on it.

    Published Jun 17, 2026self-described: Vibe CLI with GitHub Spec Kit on the free tier

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on Free Tier; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-17, Free Tier
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  31. Positive

    maelito, Hacker News commenter

    Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?Hacker News comment

    Says using Mistral Vibe CLI for a fixed 17 euros a month, "illimited", is an incredible value for money.

    Published Jun 16, 2026self-described: Daily coding on a Vibe subscription

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-16
    Not counted
    Cost predictability and limits, cost transparency: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  32. Mixed

    npodbielski, Vibe user filing a GitHub issue

    GitHub issue #762: incorrect handling of streaming response during prompt processing with local modelsGitHub issue

    Vibe 2.14 treated llama.cpp's keep-alive events as errors during long prompt processing when it should have ignored them, breaking local sessions past about 20k tokens.

    Published Jun 10, 2026self-described: Qwen 3.5 on a local llama.cpp server

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Artifact checked (log); Observed on Mistral Vibe v2.14.0
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-06-10, Mistral Vibe v2.14.0
    Counts toward
    Operational control, models and deployment: unfavorable, G3 (3 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 2.14.0 and 2.14.1

  33. Mixed

    Rare_Commercial8662, Reddit r/MistralAI poster

    Usage Limits Vibe-CLIReddit post

    A heavy day now uses 20% of the monthly Vibe CLI limit, where a month earlier it used about 10%.

    Published Jun 3, 2026self-described: Heavy daily Vibe CLI user on a paid plan

    Practitioner account, pseudonymous; direct use; counts toward Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-03
    Counts toward
    Cost predictability and limits, cost predictability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  34. Positive

    C4n4r, Reddit r/MistralAI poster

    Mistral vibe can serve any type of local model !Reddit post

    C4n4r runs a local Qwen model in Vibe for small refactors and switches to Mistral Medium for bigger parts, which saves on token use.

    Published Jun 3, 2026self-described: Uses Mistral as default AI provider and LM Studio for local models

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on Qwen 3.6
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-06-03, Qwen 3.6
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with Qwen 3.6 in LM Studio and Mistral Medium

  35. Mixed

    port11, Hacker News commenter

    Comment on: Notes from the Mistral AI Now SummitHacker News comment

    Devstral keeps getting better, and port11 thinks the Vibe harness is what holds it back.

    Published May 30, 2026self-described: Follows Mistral's products

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Opinion
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-30
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  36. Mixed

    KronisLV, Hacker News commenter

    Comment on: Notes from the Mistral AI Now SummitHacker News comment

    On dev tasks Vibe was okay but not great and worse than Anthropic's models. At 20 euros a month it was a fair deal, except the 200k context would be a deal breaker in many cases.

    Published May 29, 2026self-described: Usually works with Anthropic's models; tried a Vibe subscription on dev tasks

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-29
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Delivered outcomes, context handling: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Cost predictability and limits, cost transparency: favorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe subscription with Mistral Medium 3.5

  37. Mixed

    phillc73, on a two-user Mistral Team plan

    Comment on: Microsoft starts canceling Claude Code licensesHacker News comment

    phillc73 hit the Pro monthly limit, spent another 40 euros on pay-as-you-go in one evening, and moved to a 60 euro Team plan for two users without knowing how its limits work.

    Published May 23, 2026self-described: Moved from Pro to a Team plan for two users after hitting the monthly limit

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Observed on Mistral Le Chat Teams; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-23, Mistral Le Chat Teams
    Not counted
    Cost predictability and limits, limits in practice: repeats a stronger account in its group
    Not counted
    Cost predictability and limits, cost transparency: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Very small team
    Evidence
    Reported
    Applies to
    Still applicable

  38. Mixed

    bk138, Pro plan user filing a GitHub issue

    GitHub issue #707: neither auto-compaction nor manual /compact workGitHub issue

    On two large codebases, Vibe 2.10.1 hit the model's context limit and neither automatic nor manual compaction could recover the session.

    Published May 21, 2026self-described: Analysis of two large codebases

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Observed on v2.10.1 on a Pro Plan; Artifact checked (log)
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-05-21, v2.10.1 on a Pro Plan
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)
    Not counted
    Reliability, regressions: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 2.10.1 on Pro

  39. Positive

    Tosse101, Reddit r/MistralAI poster

    Got Vibe Skills Working: Here's What I Learned (And What Still Needs Fixing)Reddit post

    Recent updates made Vibe far more consistent for Tosse101, with no more garbled Unicode or model switching, though it still writes invalid skills and its compaction forgets too much.

    Published May 17, 2026self-described: Writes custom skills for Vibe

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-05-17
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Reliability, run stability: mixed, G1 (1 unit before bounds), capped: C-relevance, C-origin

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  40. Mixed

    creinelt, Vibe user filing a GitHub issue

    GitHub issue #664: Unix Commands Executed on Windows and System Prompt Not EnforcedGitHub issue

    On Windows 11 with a PowerShell-only custom prompt, Vibe 2.9.3 kept issuing Unix commands that failed and wasted tokens.

    Published May 4, 2026self-described: Windows 11 and PowerShell

    Practitioner account, pseudonymous; structured test; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Artifact checked (log); Observed on vibe 2.9.3
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    2 artifacts (log)
    Date and version
    2026-05-04, vibe 2.9.3
    Counts toward
    Delivered outcomes, correctness: unfavorable, G3 (3 units before bounds)
    Not counted
    Delivered outcomes, task completion: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 2.9.3

  41. Mixed

    mark_l_watson, Hacker News commenter

    Comment on: Mistral Medium 3.5Hacker News comment

    Vibe was really nice for US$15 a month but less effective than Gemini with Antigravity and Gemini CLI, so another one-month test is planned for later.

    Published Apr 29, 2026self-described: Pays for several AI coding plans and evaluates each by month

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on $15/month
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-04-29, $15/month
    Counts toward
    Delivered outcomes, task completion: mixed, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Cost predictability and limits, cost transparency: favorable, G2 (2 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  42. Negative

    andhuman, Hacker News commenter

    Comment on: Mistral Medium 3.5Hacker News comment

    The Vibe CLI is really bad on Windows, which Mistral does not officially support, and cannot get find and replace right there.

    Published Apr 29, 2026self-described: Windows user

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-04-29
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  43. Positive

    qznc, Hacker News commenter

    Comment on: Mistral built a $14B AI empire by not being AmericanHacker News comment

    A week on the free tier hit web search limits but not Devstral 2 limits, and Vibe was fine for closely watched work, the way they use Claude Code.

    Published Apr 27, 2026self-described: A week on the Vibe free tier, working the way they use Claude Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on free tier
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-04-27, free tier
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance
    Not counted
    Cost predictability and limits, limits in practice: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe free tier with Devstral 2

  44. Mixed

    BrunoBernardino, Hacker News poster

    Ask HN: Cursor alternative, EU-based or privacy-focused?Hacker News post

    For small features that are quick to verify, Vibe worked well enough, but it is less neatly integrated than Cursor, and Bruno wants an EU-based or privacy-focused option.

    Published Apr 24, 2026self-described: Cursor user looking for an EU-based or privacy-focused agent for small, verifiable changes

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-04-24
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  45. Positive

    neph1010, Reddit r/LocalLLaMA poster

    Local agent win with Mistral Vibe and Qwen 3.5 27B: Transcribe story from PDFReddit post

    Vibe drove a local Qwen 3.5 27B through a long PDF transcription, after neph1010 worked around tool-call failures and output-token limits by hand.

    Published Mar 22, 2026self-described: Qwen 3.5 27B on llama.cpp, with bash approvals left on

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on Qwen3.5-27B-UD-Q5_K_XL.gguf
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-03-22, Qwen3.5-27B-UD-Q5_K_XL.gguf
    Counts toward
    Delivered outcomes, task completion: favorable, G2 (2 units before bounds)
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Not counted
    Operational control, execution control: repeats a stronger account in its group

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with Qwen 3.5 27B

  46. Negative

    arthurjean, Hacker News commenter and daily Claude Code user

    Comment on: OpenCode - Open source AI coding agentHacker News comment

    arthurjean stayed on Claude Code and ranks OpenCode well above Codex, Gemini CLI, or Mistral Vibe from their own use.

    Published Mar 21, 2026self-described: Compared OpenCode, Codex, Gemini CLI, and Mistral Vibe

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-21
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  47. Positive

    chucky_z, Hacker News commenter

    Comment on: Leanstral: Open-source agent for trustworthy coding and formal proof engineeringHacker News comment

    Using Mistral models with the Vibe CLI every day, chucky_z calls Mistral the preferred model vendor and usually starts there before Gemini, Claude, or GPT.

    Published Mar 16, 2026self-described: Uses Mistral models and the Vibe CLI daily beside Gemini, Claude, and GPT models

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on mistral-medium-3.1
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-16, mistral-medium-3.1
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  48. Mixed

    asimovDev, Hacker News commenter

    Comment on: Right-sizes LLM models to your system's RAM, CPU, and GPUHacker News comment

    On a local model, Vibe ran out of context at about 16k tokens on a project under 1,000 lines, and raising the limit made a prompt take about 10 minutes.

    Published Mar 2, 2026self-described: Local models in LM Studio for a small C codebase

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-02
    Counts toward
    Delivered outcomes, context handling: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  49. Negative

    SyneRyder, Hacker News commenter

    Comment on: Qwen3.5 122B and 35B models offer Sonnet 4.5 performance on local computersHacker News comment

    SyneRyder calls the Vibe harness abysmal: asked to configure local MCP servers, it searched the machine for Minecraft Protocol servers, and blames the harness more than the model.

    Published Mar 1, 2026self-described: Tried Vibe with Devstral for local MCP setup

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-03-01
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with Devstral 2

  50. Positive

    rcarmo, Hacker News commenter who runs coding agents in per-project containers

    Comment on: Pi - A minimal terminal coding harnessHacker News comment

    Of the many agents rcarmo has run, Vibe had the preferred user experience until Pi arrived.

    Published Feb 25, 2026self-described: Has tried most terminal agents in an agentbox setup

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-02-25
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  51. Mixed

    abhikul0, Hacker News commenter

    Comment on: The Engine Behind the HypeHacker News comment

    Testing small local models, abhikul0 found Vibe and the other big agents send 7 to 10k tokens of initial prompt, slow on a laptop, and settled on Pi's 1.5k instead.

    Published Feb 24, 2026self-described: Small local models on an M3 Pro laptop

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-02-24
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  52. Positive

    slopinthebag, Hacker News commenter

    Comment on: European Tech AlternativesHacker News comment

    Vibe is cheap for what you get and slopinthebag has not hit its limits, though Opus and Codex are better for coding.

    Published Feb 19, 2026self-described: Uses Vibe and Le Chat; writes little code with it

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-02-19
    Not counted
    Cost predictability and limits, limits in practice: repeats a stronger account in its group
    Not counted
    Operational control, models and deployment: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  53. Positive

    Charles Azam, engineer and blogger

    I Forked 4 cli coding agents to Run the Same Model. A scaffholding deepdive.Practitioner blog

    With the same GLM-4.7 model, Vibe scored 0.35 on Terminal-Bench 2.0 against 0.29 for Claude Code and 0.15 for Codex, which Charles Azam credits to Vibe's edit tools and adapters.

    Published Feb 10, 2026self-described: Forked Codex, Gemini CLI, and Vibe to run GLM-4.7 on Terminal-Bench 2.0

    Practitioner account; structured test; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Ran a structured test; Artifact checked (benchmark output); Observed on GLM-4.7; GLM-5
    Role
    Name unknown; employer unknown; role unknown
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Ran a structured test
    Support
    1 artifact (benchmark output)
    Date and version
    2026-02-10, GLM-4.7; GLM-5
    Counts toward
    Delivered outcomes, measured outcomes: favorable, G1 (1 unit before bounds), capped: C-relationship, C-unknown-control
    Counts toward
    Operational control, execution control: mixed, G1 (1 unit before bounds), capped: C-relationship, C-unknown-control
    Counts toward
    Operational control, models and deployment: favorable, G1 (1 unit before bounds), capped: C-relationship, C-unknown-control

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Engineering Blogs & Studies
    Who
    Individual practitioner
    Evidence
    Measured
    Applies to
    Still applicable
    Observed on
    Vibe fork running GLM-4.7

  54. Mixed

    Consumerbot37427, Reddit r/LocalLLaMA poster

    Mistral Vibe vs Claude Code vs OpenAI Codex vs Opencode/others? Best coding model for 92GB?Reddit post

    Vibe with Devstral Small refactored a small Python project well on a 92 GB MacBook, but stalled near 100k tokens of context, and other local models failed its tool calls or looped.

    Published Feb 2, 2026self-described: Devstral Small in LM Studio on a 92 GB MacBook

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on Devstral Small; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-02-02, Devstral Small
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds)
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)
    Counts toward
    Operational control, models and deployment: unfavorable, G1 (1 unit before bounds)
    Counts toward
    Delivered outcomes, correctness: unfavorable, G1 (1 unit before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with Devstral Small in LM Studio

  55. Positive

    vga42, Hacker News commenter

    Comment on: Mistral Launches Vibe 2.0Hacker News comment

    After a few hours with Vibe 2.0, vga42 found it pretty great and welcomed a strong European option; the Zed integration was broken at the time while the CLI worked.

    Published Jan 28, 2026self-described: Replacing American tech with European tech

    Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-28
    Not counted
    Adoption and upkeep, setup: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 2.0

  56. Mixed

    sdbbs, paying Vibe user filing a GitHub issue

    GitHub issue #275: Usage rate limits unclearGitHub issue

    A paying user kept hitting a rate limit error with session context to spare and no way to tell which limit applied or when it would lift.

    Published Jan 26, 2026self-described: A few weeks on a paid plan

    Practitioner account, pseudonymous; direct use; counts toward Reliability, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; Customer of Mistral Vibe; Used it directly; Artifact checked (log); Observed on vibe 1.3.5
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    2 artifacts (log)
    Date and version
    2026-01-26, vibe 1.3.5
    Counts toward
    Cost predictability and limits, cost transparency: unfavorable, G3 (3 units before bounds)
    Counts toward
    Reliability, service availability: unfavorable, G3 (3 units before bounds)
    Not counted
    Cost predictability and limits, cost predictability: repeats a stronger account in its group

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  57. Mixed

    robinheghan, Vibe user filing a GitHub issue

    GitHub issue #272: search_replace tool struggles with certain patternsGitHub issue

    Vibe's search_replace tool failed on unescaped special characters and looped, while OpenCode ran the same prompt without trouble, so robinheghan attributes the failure to the tool and does not blame the model.

    Published Jan 25, 2026self-described: Documentation refactor in the Gren language core repository

    Practitioner account, pseudonymous; structured test; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Artifact checked (log); Observed on mistral-vibe 1.3.5
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    1 artifact (log)
    Date and version
    2026-01-25, mistral-vibe 1.3.5
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe with Devstral 2

  58. Mixed

    AppealSame4367, Reddit r/ChatGPTCoding poster

    All major AI stupid again, alternatives?Reddit post

    AppealSame4367 found the Vibe CLI almost as good as the big agents and surprisingly smart for its model. It became slow over time, was poor on large projects, and was hard to run more than two at once.

    Published Jan 21, 2026self-described: Works across several projects with several paid agents

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Reliability, Cost predictability and limits How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-21
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds)
    Counts toward
    Delivered outcomes, context handling: unfavorable, G1 (1 unit before bounds), capped: C-relevance
    Counts toward
    Cost predictability and limits, limits in practice: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  59. Mixed

    jdwx, Vibe user filing a GitHub issue

    GitHub issue #255: Mistral-Vibe produces multiple user messages in a row after interruptsGitHub issue

    After an interrupt, Vibe sends two user messages in a row, which the Devstral 2 chat template rejects on a local llama.cpp server.

    Published Jan 16, 2026self-described: Devstral 2 on a local llama.cpp server

    Practitioner account, pseudonymous; direct use; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Artifact checked (log); Observed on mistral-vibe v1.3.5
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2026-01-16, mistral-vibe v1.3.5
    Counts toward
    Reliability, run stability: unfavorable, G3 (3 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  60. Positive

    Aggressive-Bother470, Reddit r/LocalLLaMA poster (account since deleted; handle from the Arctic Shift archive)

    Mistral Vibe + Devstral2 Small = the perfect local combo?Reddit post

    Vibe with Devstral Small 2 just works locally at the full 256k context with almost no fiddling, and it is likely replacing Roo for this user.

    Published Jan 4, 2026self-described: Runs Devstral Small 2 at full context on three local GPUs

    Practitioner account, pseudonymous; direct use; counts toward Operational control, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on Devstral2 Small
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2026-01-04, Devstral2 Small
    Counts toward
    Adoption and upkeep, setup: favorable, G1 (1 unit before bounds)
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe with Devstral Small 2 at Q4

  61. Negative

    khimaros, Hacker News commenter

    Comment on: Claude Code gets native LSP supportHacker News comment

    Having used Crush, OpenCode, Aider, mistral-vibe, Gemini CLI, the Qwen fork, and Claude Code, khimaros names Claude Code the clear winner.

    Published Dec 23, 2025self-described: Prefers open-source, provider-agnostic agents and has used seven of them

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-23
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable

  62. Positive

    Kvit blog, written by a developer building AI tools at kvit.app

    Run-to-Run Variance in Coding Assistants: Claude Code and Vibe on 45 Bug Fixes, Ten Runs EachEngineering blog

    Across 900 runs on 45 SWE-bench-verified-mini cases, Vibe passed 37.6% and Claude Code 39.8%, a gap inside the confidence intervals, and Vibe ran about a minute faster per case.

    Published Dec 17, 2025self-described: Claude Code is the author's daily tool; Vibe ran Devstral 2

    Practitioner account; structured test; counts toward Delivered outcomes, Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Ran a structured test; Observed on Devstral 2; Artifact checked (benchmark output)
    Role
    Name unknown; employer unknown; role unknown
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Ran a structured test
    Support
    2 artifacts (benchmark output)
    Date and version
    2025-12-17, Devstral 2
    Counts toward
    Delivered outcomes, measured outcomes: mixed, G1 (1 unit before bounds), capped: C-relationship, C-unknown-control
    Counts toward
    Reliability, run stability: unfavorable, G1 (1 unit before bounds), capped: C-relationship, C-unknown-control
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship, C-unknown-control

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Engineering Blogs & Studies
    Who
    Individual practitioner
    Evidence
    Measured
    Applies to
    Still applicable
    Observed on
    Vibe with Devstral 2; Claude Code with automatic model selection

  63. No opinion stated

    cosimoiaia, Vibe user filing a GitHub issue

    GitHub issue #150: Copy and Paste not working in LinuxGitHub issue

    On Ubuntu 25.04 with Mistral Vibe v1.1.3, selecting a line shows a copied-to-clipboard message, but nothing is copied to the clipboard.

    Published Dec 14, 2025self-described: GNOME Terminal on Ubuntu 25.04

    Practitioner account, pseudonymous; direct use; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on Mistral Vibe v1.1.3
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-14, Mistral Vibe v1.1.3
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 1.1.3

  64. Positive

    jacek2023, Reddit r/LocalLLaMA poster

    Mistral Vibe CLI + Qwen 4B Q4Reddit post

    Vibe with Devstral made working changes to serious C++ code, and jacek2023 showed it browsing and explaining code even on a 4B model quantized to 4 bits.

    Published Dec 14, 2025self-described: C++ work on local models served with llama.cpp

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Observed on Qwen3-4B-Instruct-2507-Q4_K_M.gguf; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    2 artifacts (screenshot)
    Date and version
    2025-12-14, Qwen3-4B-Instruct-2507-Q4_K_M.gguf
    Counts toward
    Operational control, models and deployment: favorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, context handling: favorable, G2 (2 units before bounds)
    Not counted
    Delivered outcomes, task completion: repeats a stronger account in its group

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 1.x with Devstral 2 and Qwen3 4B

  65. Positive

    tarruda, Reddit r/LocalLLaMA poster

    The mistral-vibe CLI can work super well with gpt-ossReddit post

    With a fork that passes reasoning content back to llama.cpp, gpt-oss 20b ran well in Vibe. It was faster and better at coding than Devstral 2 in tarruda's testing, though it sometimes misused the edit tool.

    Published Dec 12, 2025self-described: Runs gpt-oss locally on llama.cpp

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on GPT-OSS 20b
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (pull request)
    Date and version
    2025-12-12, GPT-OSS 20b
    Counts toward
    Operational control, models and deployment: mixed, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, correctness: mixed, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 1.x with gpt-oss 20b on llama.cpp

  66. Mixed

    minwhoo, Vibe user filing a GitHub issue

    GitHub issue #70: Tool call not working with locally hosted vllm devstral 2 backendGitHub issue

    Against a local vLLM server running Devstral 2 Small, every request that triggered a tool call failed with a validation error.

    Published Dec 11, 2025self-described: Devstral 2 Small on a local vLLM server

    Practitioner account, pseudonymous; direct use; counts toward Operational control How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Artifact checked (log); Observed on mistral-vibe: v1.1.1
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    1 artifact (log)
    Date and version
    2025-12-11, mistral-vibe: v1.1.1
    Counts toward
    Operational control, models and deployment: unfavorable, G3 (3 units before bounds)

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck

  67. Mixed

    matt1111-hash, Vibe user filing a GitHub issue

    GitHub issue #83: Agent gets stuck in infinite loop repeating the same tool callGitHub issue

    On an audit task Vibe repeated the same successful flake8 call in a loop for 19 minutes and 4.5 million input tokens until stopped by hand.

    Published Dec 11, 2025self-described: Code audit prompt on Ubuntu

    Practitioner account, pseudonymous; structured test; counts toward Reliability How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Specific details; Observed on Vibe version: 1.1.2
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-11, Vibe version: 1.1.2
    Counts toward
    Reliability, run stability: unfavorable, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 1.1.2 with Devstral 2

  68. Negative

    optiix, Vibe user filing a GitHub issue

    GitHub issue #86: TerribleGitHub issue

    Vibe used heavy CPU, lagged next to Claude Code, and spent 80% of a day's tokens without getting a simple frontend and backend running.

    Published Dec 11, 2025self-described: Building a small web app on Ubuntu 24

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-11
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe 1.x with Devstral 2

  69. No opinion stated

    FlorentB974, Vibe user filing a GitHub issue

    GitHub issue #30: add support for HTTP/HTTPS proxy and SSL verification configurationGitHub issue

    Requests HTTP/HTTPS proxy and SSL verification settings in Vibe's config.toml, which is missing them, making Vibe difficult to use behind corporate proxies or with self-signed certificates.

    Published Dec 10, 2025self-described: Behind a corporate proxy

    Practitioner account, pseudonymous; opinion; not counted until substantiated How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Opinion; Specific details
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-10
    Not counted
    Adoption and upkeep, setup: a lead (G0), counts toward nothing until substantiated

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck

  70. Positive

    Avienir, Reddit r/LocalLLaMA poster

    Hands-on review of Mistral Vibe on large python projectReddit post

    On a 40k-line Python repository Vibe fixed a validation bug with its own temporary test and was fast and precise. Avienir found the 100k context cap reasonable for day-to-day fixes but missed resume, checkpoints, and planning.

    Published Dec 10, 2025self-described: Developer on a 40k-line Python codebase with niche frameworks

    Practitioner account, pseudonymous; structured test; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Ran a structured test; Specific details; Observed on v1.0.5
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Ran a structured test
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-10, v1.0.5
    Counts toward
    Delivered outcomes, task completion: favorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, correctness: favorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, context handling: mixed, G2 (2 units before bounds)

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 1.0.5 with Devstral 2

  71. Positive

    Simon Willison, independent developer and blogger

    mistralai/mistral-vibePractitioner blog

    Simon Willison calls Vibe a neat implementation of the terminal agent pattern with readable source and prompts, and says it did OK building a three.js game.

    Published Dec 9, 2025self-described: Read the source and had Vibe build a Space Invaders game on launch day

    Practitioner account, self-described; direct use; counts toward Delivered outcomes How GILD checked it
    Origin
    Published practitioner account
    Checked
    Self-described; Used it directly; Specific details
    Role
    Name self-described; employer unknown; role unknown
    Relationship
    Checked only from the record itself; an outside check is open
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-09
    Counts toward
    Delivered outcomes, task completion: favorable, G1 (1 unit before bounds), capped: C-relevance, C-relationship

    Checked Oct 31, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Engineering Blogs & Studies
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe 1.0 with Devstral 2

  72. Mixed

    SyneRyder, Hacker News commenter and Claude Max user

    Comment on: Mistral releases Devstral2 and Mistral Vibe CLIHacker News comment

    On launch day Vibe showed an MCP server count but offered no way to configure servers, Devstral 2 did not know what MCP was, and SyneRyder judged Mistral's models far behind Claude.

    Published Dec 9, 2025self-described: Tried Vibe on launch day alongside Claude Code

    Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Adoption and upkeep How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Used it directly; Specific details; Observed on Devstral 2
    Role
    Pseudonymous account; identity not pursued
    Relationship
    customer (self disclosed)
    How they know
    Used it directly
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-09, Devstral 2
    Counts toward
    Adoption and upkeep, setup: unfavorable, G2 (2 units before bounds)
    Counts toward
    Delivered outcomes, task completion: unfavorable, G1 (1 unit before bounds), capped: C-relevance

    Checked Oct 30, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward, pending a recheck

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Needs a recheck
    Observed on
    Vibe CLI 1.0 with Devstral 2

  73. No opinion stated

    simonw, Hacker News commenter

    Comment on: Mistral releases Devstral2 and Mistral Vibe CLIHacker News comment

    After limited time with Vibe, simonw expected a 123B Devstral 2 to fall short of Claude Code on Opus 4.5 for large tasks, such as rewriting a repository's Git history.

    Published Dec 9, 2025self-described: Daily Claude Code user who had tried Vibe briefly

    Practitioner account, pseudonymous; opinion; not counted, takes no position How GILD checked it
    Origin
    Published practitioner account
    Checked
    Pseudonymous; No tie to Mistral Vibe found in GILD's check; Opinion
    Role
    Pseudonymous account; identity not pursued
    Relationship
    No tie to Mistral Vibe found in GILD's check (byline, content disclosure, platform api profile); that is not proof none exists
    How they know
    Opinion, no use stated
    Support
    No artifact or independent corroboration recorded
    Date and version
    2025-12-09
    Not counted
    no aspect: excluded, takes no position on any assessed aspect

    Checked Oct 29, 2026 under gild-policy/1.0.0. The scorecard

    Counts toward

    Published on
    Developer Communities
    Who
    Individual practitioner
    Evidence
    Reported
    Applies to
    Still applicable
    Observed on
    Vibe CLI 1.0 with Devstral 2

Product documentation 12

Pages from Mistral AI, used to check facts for every group.

  1. Mistral pricing

    Lists Free with limited coding sessions, Pro at US$14.99 per month, and Team at US$24.99 per user per month before tax, with all-day coding in the CLI, IDE, or web. Enterprise is through sales.

    Checked Oct 25, 2026

  2. Mistral Vibe

    Describes Vibe for code across the CLI, VS Code, JetBrains, and Zed through ACP, remote agents, and Enterprise deployment on-premises, in a private cloud, or on Mistral Cloud.

    Checked Oct 25, 2026

  4. Remote agents in Vibe

    States that Mistral Medium 3.5 replaces Devstral 2 in Vibe and that remote agents run in cloud sandboxes on Pro, Team, and Enterprise.

    Checked Oct 25, 2026

  5. Configuration

    Documents Mistral Medium 3.5 as the one built-in model, GLM 5.3 among the listed models, and enable_telemetry defaulting to true.

    Checked Oct 25, 2026

  6. API keys and profiles

    States that plan usage is shared across Studio, the API, and Vibe Code, and that Vibe Code stops when it runs out unless pay-as-you-go is on.

    Checked Oct 25, 2026

  7. Using offline models

    Documents vLLM, llama.cpp, LM Studio, and Ollama, Devstral Small 2 and Mistral Small 4 hardware needs, and the settings for a fully offline setup.

    Checked Oct 25, 2026

  8. Safety, approvals, and permissions

    Documents the ask, accept-edits, smart-approve, and auto-approve modes, and that a bash allowlist replaces the default list.

    Checked Oct 25, 2026

  9. Admin config

    Documents organization and workspace config for models, MCP servers, connectors, tools, telemetry, and disabling auto-approve.

    Checked Oct 25, 2026

  10. Zero data retention

    States that Vibe CLI calls follow the zero data retention rules of the underlying API on paid plans once approved.

    Checked Oct 25, 2026

  11. Regional inference

    Documents the EU endpoint for the API at 1.1 times list price and says it does not make the control plane regional.

    Checked Oct 25, 2026

Source index

Provenance at a glance

Every source GILD read, with the original address and the context used to count it. Open a finding to filter the full cards above. On smaller screens the index lists each source once by name, cohort and date; its full record above carries the address, context and findings.

Provenance for every analyzed Signals source
SourceOriginal URLAuthor and contextWhoPublishedReview dateAppliesFindings
Comment on: Timestral: Mistral's time-series foundation modelsID hn-50151502 | Developer Communitiesnews.ycombinator.com/item?id=50151502maelito, Hacker News commenterself-described: Tested Mistral Large 4 in VibeIndividual practitionerPublished Oct 19, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Mistral models through a Vibe subscriptionID lead3-hn-50154189 | Developer Communitiesnews.ycombinator.com/item?id=50154189nozzlegear, developer using a Vibe subscription through OMPself-described: Mistral 4 and GLM accessed through OMP with a Vibe subscriptionIndividual practitionerPublished Oct 19, 2026Assessment reviewed Nov 1, 2026CurrentListed, no finding position
Comment on: Mistral Vibe and Mistral 4ID lead3-hn-50156491 | Developer Communitiesnews.ycombinator.com/item?id=50156491data-ottawa, developer using Mistral Vibeself-described: Mistral Vibe configured for Mistral 4Individual practitionerPublished Oct 19, 2026Assessment reviewed Nov 1, 2026Current
tried Vibe CLI for the first time. What a hot mess.ID rd-1x0ylv6 | Developer Communitieswww.reddit.com/r/MistralAI/comments/1x0ylv6/tried_vibe_cli_for_the_first_time_what_a_hot_mess/themflyingjaffacakes, Reddit r/MistralAI posterself-described: Long-term supporter of EU AI; uses the Mistral API for privacy-related callsIndividual practitionerPublished Oct 8, 2026Assessment reviewed Nov 1, 2026Current
Comment on: Mistral Large 4ID hn-49980909 | Developer Communitiesnews.ycombinator.com/item?id=49980909phillc73, Hacker News commenterself-described: Heavy user on two Vibe subscriptionsIndividual practitionerPublished Oct 6, 2026Assessment reviewed Nov 1, 2026Current
Mistral Vibe Code CLI is GREAT!ID rd-1wum7h4 | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wum7h4/mistral_vibe_code_cli_is_great/Altruistic_Panda_420, Reddit r/MistralAI posterself-described: Has used Pi, Claude Code, Antigravity, Codex, and others on the DeepSeek APIIndividual practitionerPublished Oct 1, 2026Assessment reviewed Nov 1, 2026Current
Mistral Vibe Shell Permission Bypass Leading to Arbitrary Code ExecutionID bl-secmate | Engineering Blogs & Studiesblog.secmate.dev/posts/mistral-vibe-cve-2026-87987-cve-2026-87984/Maxime Rossi Bellom and Ramtine Tofighi Shirazi, security researchers at SecMateself-described: Security review of Vibe 2.25.0Professional teamPublished Sep 23, 2026Assessment reviewed Nov 1, 2026Needs a recheck
GLM is the most interesting Mistral Vibe development. But is Vibe Pro competitive enough?ID rd-1wnwgrq | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wnwgrq/glm_is_the_most_interesting_mistral_vibe/ublistening, Reddit r/MistralAI posterself-described: Pays for several AI tools and weighs Vibe Pro against themIndividual practitionerPublished Sep 23, 2026Assessment reviewed Nov 1, 2026Current
Today, Vibe doesn't care about "plan mode"ID rd-1wo9kbf | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wo9kbf/today_vibe_doesnt_care_about_plan_mode/RedditPolux, Reddit r/MistralAI posterself-described: Vibe on two machines and projects with GLM-5.3Individual practitionerPublished Sep 23, 2026Assessment reviewed Nov 1, 2026Needs a recheck
Four things I got wrong about Vibe CLI's permission config (2.25.5)ID rd-1wn1p7j | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wn1p7j/four_things_i_got_wrong_about_vibe_clis/Difficult-Sugar-4862, Reddit r/MistralAI posterself-described: Scopes agents with .vibe/agents permission profilesIndividual practitionerPublished Sep 22, 2026Assessment reviewed Nov 1, 2026Still applicable
New "unified harness" is unified in ignoring my agent configsID rd-1wmmwdm | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wmmwdm/new_unified_harness_is_unified_in_ignoring_my/Martypx00, Reddit r/MistralAI posterself-described: Uses custom agents and subagents in the Vibe CLIIndividual practitionerPublished Sep 21, 2026Assessment reviewed Nov 1, 2026Needs a recheck
GitHub issue #1113: Unified Harness ignores allowlist on file toolsID gh-1113 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/1113Simon-LM, Vibe user filing a GitHub issueself-described: Agent profiles with write allowlistsIndividual practitionerPublished Sep 18, 2026Assessment reviewed Nov 1, 2026Needs a recheck
Using Mistral for code at workID rd-1wjj1ey | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wjj1ey/using_mistral_for_code_at_work/Altrollique, Reddit r/MistralAI poster and regular Claude userself-described: Coding at work; tried Vibe with GLM-5.2 over the summerIndividual practitionerPublished Sep 18, 2026Assessment reviewed Nov 1, 2026Still applicable
Long rant about the stupidity that is Mistral billing. I want to understand the logic.ID rd-1wjk2ng | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wjk2ng/long_rant_about_the_stupidity_that_is_mistral/infinitescript, Reddit r/MistralAI poster on Proself-described: Signed up for Pro to use VibeIndividual practitionerPublished Sep 18, 2026Assessment reviewed Nov 1, 2026Still applicable
Regional inferenceID rd-1wjk4n9 | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wjk4n9/regional_inference/West_Passion_1665, Reddit r/MistralAI posterself-described: Vibe CLI user who wants all data kept in the EUIndividual practitionerPublished Sep 18, 2026Assessment reviewed Nov 1, 2026Still applicable
Mistral doesn't give us sovereignty, or respect our privacy!ID rd-1whxzef | Developer Communitieswww.reddit.com/r/MistralAI/comments/1whxzef/mistral_doesnt_give_us_sovereignty_or_respect_our/lucid_supernova, Reddit r/MistralAI posterself-described: Switched to Mistral for privacyIndividual practitionerPublished Sep 16, 2026Assessment reviewed Nov 1, 2026Still applicable
I probed all 46 models exposed to my Mistral Free account - even the Vibe CLI models have a 0 RPM limitID rd-1wcj6zo | Developer Communitieswww.reddit.com/r/MistralAI/comments/1wcj6zo/i_probed_all_46_models_exposed_to_my_mistral_free/MrViking2k19, Reddit r/MistralAI posterself-described: Trying Vibe 2.25.1 on a Free accountIndividual practitionerPublished Sep 10, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Vibe Code: GLM 5.2 is now availableID hn-49561044 | Developer Communitiesnews.ycombinator.com/item?id=49561044maxhille, Hacker News commenterself-described: Pro subscriber who also runs a local Qwen modelIndividual practitionerPublished Sep 4, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Can I opt out of my input or output data being used for training?ID hn-49536706 | Developer Communitiesnews.ycombinator.com/item?id=49536706jnurmine, Hacker News commenterself-described: Uses Claude in Kiro and Mistral VibeIndividual practitionerPublished Sep 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Can I opt out of my input or output data being used for training?ID hn-49536737 | Developer Communitiesnews.ycombinator.com/item?id=49536737evanjrowley, Hacker News commenterself-described: Plans with GLM-5.2 through Mistral Studio and implements with a Vibe key on a basic planIndividual practitionerPublished Sep 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Vibe Team plan defaultsID lead3-hn-49538451 | Developer Communitiesnews.ycombinator.com/item?id=49538451teekert, Team-plan administrator discussing organization-wide data controlsself-described: Mistral Vibe Team plan organization settingsProfessional teamPublished Sep 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Vibe Team plan training defaultID lead3-hn-49538530 | Developer Communitiesnews.ycombinator.com/item?id=49538530teekert, Team-plan administrator discussing organization-wide data controlsself-described: Mistral Vibe Team plan organization settingsProfessional teamPublished Sep 2, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #997: Remote Code Execution via worktree creation (git attribute filter execution)ID gh-997 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/997therealcoiffeur, security researcher filing a GitHub issueself-described: A working exploit against the --worktree flagIndividual practitionerPublished Aug 12, 2026Assessment reviewed Nov 1, 2026Still applicable
Why do Vibe CLI and Vibe VS Code Extension perform so differently? (PRO subscription)ID rd-1vdfprr | Developer Communitieswww.reddit.com/r/MistralAI/comments/1vdfprr/why_do_vibe_cli_and_vibe_vs_code_extension/Guilty-Pride6761, Reddit r/MistralAI poster on Proself-described: Python audio processing scriptIndividual practitionerPublished Aug 2, 2026Assessment reviewed Nov 1, 2026Still applicable
vibe-cli, offline models (ollama), don't preserve context history between messagesID rd-1v9c9ud | Developer Communitieswww.reddit.com/r/MistralAI/comments/1v9c9ud/vibecli_offline_models_ollama_dont_preserve/kodmasin, Reddit r/MistralAI posterself-described: Vibe CLI with offline models through OllamaIndividual practitionerPublished Jul 28, 2026Assessment reviewed Nov 1, 2026Still applicable
Vibe CLI unusable tonightID rd-1v1vhbt | Developer Communitieswww.reddit.com/r/MistralAI/comments/1v1vhbt/vibe_cli_unusable_tonight/tom4112, Reddit r/MistralAI posterself-described: Regular Vibe CLI userIndividual practitionerPublished Jul 20, 2026Assessment reviewed Nov 1, 2026Still applicable
Mistral CLI, what's with the Git commit signatures?ID rd-1umxpjq | Developer Communitieswww.reddit.com/r/MistralAI/comments/1umxpjq/mistral_cli_whats_with_the_git_commit_signatures/bunaventure, Reddit r/MistralAI poster and paying subscriberself-described: Uses the Vibe CLI with GitIndividual practitionerPublished Jul 4, 2026Assessment reviewed Nov 1, 2026Still applicable
A story of how Mistral Vibe CLI failed to install MCPID rd-1uldzx9 | Developer Communitieswww.reddit.com/r/MistralAI/comments/1uldzx9/a_story_of_how_mistral_vibe_cli_failed_to_install/SkyPL, Reddit r/MistralAI posterself-described: Testing several agent harnesses on WindowsIndividual practitionerPublished Jul 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Leanstral 1.5ID hn-48740785 | Developer Communitiesnews.ycombinator.com/item?id=48740785adev_, Hacker News commenterself-described: C++ and Python work, with Claude as a fallbackIndividual practitionerPublished Jun 30, 2026Assessment reviewed Nov 1, 2026Still applicable
Constantly getting stuck in thinking and hitting PoolTimeout error while codingID rd-1u8m7qq | Developer Communitieswww.reddit.com/r/MistralAI/comments/1u8m7qq/constantly_getting_stuck_in_thinking_and_hitting/InsideMikesWorld, Reddit r/MistralAI posterself-described: Vibe CLI with GitHub Spec Kit on the free tierIndividual practitionerPublished Jun 17, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?ID hn-48553274 | Developer Communitiesnews.ycombinator.com/item?id=48553274maelito, Hacker News commenterself-described: Daily coding on a Vibe subscriptionIndividual practitionerPublished Jun 16, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #762: incorrect handling of streaming response during prompt processing with local modelsID gh-762 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/762npodbielski, Vibe user filing a GitHub issueself-described: Qwen 3.5 on a local llama.cpp serverIndividual practitionerPublished Jun 10, 2026Assessment reviewed Nov 1, 2026Needs a recheck
Usage Limits Vibe-CLIID rd-1tvmomu | Developer Communitieswww.reddit.com/r/MistralAI/comments/1tvmomu/usage_limits_vibecli/Rare_Commercial8662, Reddit r/MistralAI posterself-described: Heavy daily Vibe CLI user on a paid planIndividual practitionerPublished Jun 3, 2026Assessment reviewed Nov 1, 2026Still applicable
Mistral vibe can serve any type of local model !ID rd-1tvte6q | Developer Communitieswww.reddit.com/r/MistralAI/comments/1tvte6q/mistral_vibe_can_serve_any_type_of_local_model/C4n4r, Reddit r/MistralAI posterself-described: Uses Mistral as default AI provider and LM Studio for local modelsIndividual practitionerPublished Jun 3, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Notes from the Mistral AI Now SummitID hn-48333399 | Developer Communitiesnews.ycombinator.com/item?id=48333399port11, Hacker News commenterself-described: Follows Mistral's productsIndividual practitionerPublished May 30, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Notes from the Mistral AI Now SummitID hn-48329848 | Developer Communitiesnews.ycombinator.com/item?id=48329848KronisLV, Hacker News commenterself-described: Usually works with Anthropic's models; tried a Vibe subscription on dev tasksIndividual practitionerPublished May 29, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Microsoft starts canceling Claude Code licensesID hn-48246706 | Developer Communitiesnews.ycombinator.com/item?id=48246706phillc73, on a two-user Mistral Team planself-described: Moved from Pro to a Team plan for two users after hitting the monthly limitVery small teamPublished May 23, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #707: neither auto-compaction nor manual /compact workID gh-707 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/707bk138, Pro plan user filing a GitHub issueself-described: Analysis of two large codebasesIndividual practitionerPublished May 21, 2026Assessment reviewed Nov 1, 2026Needs a recheck
Got Vibe Skills Working: Here's What I Learned (And What Still Needs Fixing)ID rd-1tfmscc | Developer Communitieswww.reddit.com/r/MistralAI/comments/1tfmscc/got_vibe_skills_workingheres_what_i_learned_and/Tosse101, Reddit r/MistralAI posterself-described: Writes custom skills for VibeIndividual practitionerPublished May 17, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #664: Unix Commands Executed on Windows and System Prompt Not EnforcedID gh-664 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/664creinelt, Vibe user filing a GitHub issueself-described: Windows 11 and PowerShellIndividual practitionerPublished May 4, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Medium 3.5ID hn-47950300 | Developer Communitiesnews.ycombinator.com/item?id=47950300mark_l_watson, Hacker News commenterself-described: Pays for several AI coding plans and evaluates each by monthIndividual practitionerPublished Apr 29, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Medium 3.5ID hn-47952102 | Developer Communitiesnews.ycombinator.com/item?id=47952102andhuman, Hacker News commenterself-described: Windows userIndividual practitionerPublished Apr 29, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral built a $14B AI empire by not being AmericanID hn-47923667 | Developer Communitiesnews.ycombinator.com/item?id=47923667qznc, Hacker News commenterself-described: A week on the Vibe free tier, working the way they use Claude CodeIndividual practitionerPublished Apr 27, 2026Assessment reviewed Nov 1, 2026Still applicable
Ask HN: Cursor alternative, EU-based or privacy-focused?ID hn-47893545 | Developer Communitiesnews.ycombinator.com/item?id=47893545BrunoBernardino, Hacker News posterself-described: Cursor user looking for an EU-based or privacy-focused agent for small, verifiable changesIndividual practitionerPublished Apr 24, 2026Assessment reviewed Nov 1, 2026Still applicable
Local agent win with Mistral Vibe and Qwen 3.5 27B: Transcribe story from PDFID rd-1s0f98b | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1s0f98b/local_agent_win_with_mistral_vibe_and_qwen_35_27b/neph1010, Reddit r/LocalLLaMA posterself-described: Qwen 3.5 27B on llama.cpp, with bash approvals left onIndividual practitionerPublished Mar 22, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: OpenCode - Open source AI coding agentID hn-47469135 | Developer Communitiesnews.ycombinator.com/item?id=47469135arthurjean, Hacker News commenter and daily Claude Code userself-described: Compared OpenCode, Codex, Gemini CLI, and Mistral VibeIndividual practitionerPublished Mar 21, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Leanstral: Open-source agent for trustworthy coding and formal proof engineeringID hn-47405753 | Developer Communitiesnews.ycombinator.com/item?id=47405753chucky_z, Hacker News commenterself-described: Uses Mistral models and the Vibe CLI daily beside Gemini, Claude, and GPT modelsIndividual practitionerPublished Mar 16, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Right-sizes LLM models to your system's RAM, CPU, and GPUID hn-47214795 | Developer Communitiesnews.ycombinator.com/item?id=47214795asimovDev, Hacker News commenterself-described: Local models in LM Studio for a small C codebaseIndividual practitionerPublished Mar 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Qwen3.5 122B and 35B models offer Sonnet 4.5 performance on local computersID hn-47207497 | Developer Communitiesnews.ycombinator.com/item?id=47207497SyneRyder, Hacker News commenterself-described: Tried Vibe with Devstral for local MCP setupIndividual practitionerPublished Mar 1, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Pi - A minimal terminal coding harnessID hn-47151242 | Developer Communitiesnews.ycombinator.com/item?id=47151242rcarmo, Hacker News commenter who runs coding agents in per-project containersself-described: Has tried most terminal agents in an agentbox setupIndividual practitionerPublished Feb 25, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: The Engine Behind the HypeID hn-47134991 | Developer Communitiesnews.ycombinator.com/item?id=47134991abhikul0, Hacker News commenterself-described: Small local models on an M3 Pro laptopIndividual practitionerPublished Feb 24, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: European Tech AlternativesID hn-47070916 | Developer Communitiesnews.ycombinator.com/item?id=47070916slopinthebag, Hacker News commenterself-described: Uses Vibe and Le Chat; writes little code with itIndividual practitionerPublished Feb 19, 2026Assessment reviewed Nov 1, 2026Still applicable
I Forked 4 cli coding agents to Run the Same Model. A scaffholding deepdive.ID bl-azam | Engineering Blogs & Studiescharlesazam.com/blog/deepdive-benchmark/Charles Azam, engineer and bloggerself-described: Forked Codex, Gemini CLI, and Vibe to run GLM-4.7 on Terminal-Bench 2.0Individual practitionerPublished Feb 10, 2026Assessment reviewed Nov 1, 2026Still applicable
Mistral Vibe vs Claude Code vs OpenAI Codex vs Opencode/others? Best coding model for 92GB?ID rd-1qtg3sm | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1qtg3sm/mistral_vibe_vs_claude_code_vs_openai_codex_vs/Consumerbot37427, Reddit r/LocalLLaMA posterself-described: Devstral Small in LM Studio on a 92 GB MacBookIndividual practitionerPublished Feb 2, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral Launches Vibe 2.0ID hn-46791793 | Developer Communitiesnews.ycombinator.com/item?id=46791793vga42, Hacker News commenterself-described: Replacing American tech with European techIndividual practitionerPublished Jan 28, 2026Assessment reviewed Nov 1, 2026Needs a recheck
GitHub issue #275: Usage rate limits unclearID gh-275 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/275sdbbs, paying Vibe user filing a GitHub issueself-described: A few weeks on a paid planIndividual practitionerPublished Jan 26, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #272: search_replace tool struggles with certain patternsID gh-272 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/272robinheghan, Vibe user filing a GitHub issueself-described: Documentation refactor in the Gren language core repositoryIndividual practitionerPublished Jan 25, 2026Assessment reviewed Nov 1, 2026Needs a recheck
All major AI stupid again, alternatives?ID rd-1qitqu3 | Developer Communitieswww.reddit.com/r/ChatGPTCoding/comments/1qitqu3/all_major_ai_stupid_again_alternatives/AppealSame4367, Reddit r/ChatGPTCoding posterself-described: Works across several projects with several paid agentsIndividual practitionerPublished Jan 21, 2026Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #255: Mistral-Vibe produces multiple user messages in a row after interruptsID gh-255 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/255jdwx, Vibe user filing a GitHub issueself-described: Devstral 2 on a local llama.cpp serverIndividual practitionerPublished Jan 16, 2026Assessment reviewed Nov 1, 2026Still applicable
Mistral Vibe + Devstral2 Small = the perfect local combo?ID rd-1q3epye | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1q3epye/mistral_vibe_devstral2_small_the_perfect_local/Aggressive-Bother470, Reddit r/LocalLLaMA poster (account since deleted; handle from the Arctic Shift archive)self-described: Runs Devstral Small 2 at full context on three local GPUsIndividual practitionerPublished Jan 4, 2026Assessment reviewed Nov 1, 2026Still applicable
Comment on: Claude Code gets native LSP supportID hn-46361349 | Developer Communitiesnews.ycombinator.com/item?id=46361349khimaros, Hacker News commenterself-described: Prefers open-source, provider-agnostic agents and has used seven of themIndividual practitionerPublished Dec 23, 2025Assessment reviewed Nov 1, 2026Still applicable
Run-to-Run Variance in Coding Assistants: Claude Code and Vibe on 45 Bug Fixes, Ten Runs EachID bl-kvit | Engineering Blogs & Studiesblog.kvit.app/posts/variance-claude-vibe/Kvit blog, written by a developer building AI tools at kvit.appself-described: Claude Code is the author's daily tool; Vibe ran Devstral 2Individual practitionerPublished Dec 17, 2025Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #150: Copy and Paste not working in LinuxID gh-150 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/150cosimoiaia, Vibe user filing a GitHub issueself-described: GNOME Terminal on Ubuntu 25.04Individual practitionerPublished Dec 14, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Mistral Vibe CLI + Qwen 4B Q4ID rd-1pmmj5o | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1pmmj5o/mistral_vibe_cli_qwen_4b_q4/jacek2023, Reddit r/LocalLLaMA posterself-described: C++ work on local models served with llama.cppIndividual practitionerPublished Dec 14, 2025Assessment reviewed Nov 1, 2026Still applicable
The mistral-vibe CLI can work super well with gpt-ossID rd-1pl3kzb | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1pl3kzb/the_mistralvibe_cli_can_work_super_well_with/tarruda, Reddit r/LocalLLaMA posterself-described: Runs gpt-oss locally on llama.cppIndividual practitionerPublished Dec 12, 2025Assessment reviewed Nov 1, 2026Needs a recheck
GitHub issue #70: Tool call not working with locally hosted vllm devstral 2 backendID gh-70 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/70minwhoo, Vibe user filing a GitHub issueself-described: Devstral 2 Small on a local vLLM serverIndividual practitionerPublished Dec 11, 2025Assessment reviewed Nov 1, 2026Needs a recheck
GitHub issue #83: Agent gets stuck in infinite loop repeating the same tool callID gh-83 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/83matt1111-hash, Vibe user filing a GitHub issueself-described: Code audit prompt on UbuntuIndividual practitionerPublished Dec 11, 2025Assessment reviewed Nov 1, 2026Still applicable
GitHub issue #86: TerribleID gh-86 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/86optiix, Vibe user filing a GitHub issueself-described: Building a small web app on Ubuntu 24Individual practitionerPublished Dec 11, 2025Assessment reviewed Nov 1, 2026Needs a recheck
GitHub issue #30: add support for HTTP/HTTPS proxy and SSL verification configurationID gh-30 | Developer Communitiesgithub.com/mistralai/mistral-vibe/issues/30FlorentB974, Vibe user filing a GitHub issueself-described: Behind a corporate proxyIndividual practitionerPublished Dec 10, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Hands-on review of Mistral Vibe on large python projectID rd-1pj12ix | Developer Communitieswww.reddit.com/r/LocalLLaMA/comments/1pj12ix/handson_review_of_mistral_vibe_on_large_python/Avienir, Reddit r/LocalLLaMA posterself-described: Developer on a 40k-line Python codebase with niche frameworksIndividual practitionerPublished Dec 10, 2025Assessment reviewed Nov 1, 2026Still applicable
mistralai/mistral-vibeID bl-willison | Engineering Blogs & Studiessimonwillison.net/2025/Dec/9/mistral-vibe/Simon Willison, independent developer and bloggerself-described: Read the source and had Vibe build a Space Invaders game on launch dayIndividual practitionerPublished Dec 9, 2025Assessment reviewed Nov 1, 2026Still applicable
Comment on: Mistral releases Devstral2 and Mistral Vibe CLIID hn-46208256 | Developer Communitiesnews.ycombinator.com/item?id=46208256SyneRyder, Hacker News commenter and Claude Max userself-described: Tried Vibe on launch day alongside Claude CodeIndividual practitionerPublished Dec 9, 2025Assessment reviewed Nov 1, 2026Needs a recheck
Comment on: Mistral releases Devstral2 and Mistral Vibe CLIID hn-46211642 | Developer Communitiesnews.ycombinator.com/item?id=46211642simonw, Hacker News commenterself-described: Daily Claude Code user who had tried Vibe brieflyIndividual practitionerPublished Dec 9, 2025Assessment reviewed Nov 1, 2026Still applicable
Mistral pricingID pd-01 | Product Documentationmistral.ai/pricingMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Mistral VibeID pd-02 | Product Documentationmistral.ai/products/vibeMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Introducing Devstral 2 and Mistral Vibe CLIID pd-03 | Product Documentationmistral.ai/news/devstral-2-vibe-cliMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Remote agents in VibeID pd-04 | Product Documentationmistral.ai/news/vibe-remote-agents-mistral-medium-3-5Mistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
ConfigurationID pd-05 | Product Documentationdocs.mistral.ai/vibe/code/cli/configurationMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
API keys and profilesID pd-06 | Product Documentationdocs.mistral.ai/vibe/code/cli/api-keys-profilesMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Using offline modelsID pd-07 | Product Documentationdocs.mistral.ai/vibe/code/cli/offline-modelsMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Safety, approvals, and permissionsID pd-08 | Product Documentationdocs.mistral.ai/vibe/code/safety-approvals-permissionsMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Admin configID pd-09 | Product Documentationdocs.mistral.ai/vibe/code/cli/admin-configMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Zero data retentionID pd-10 | Product Documentationdocs.mistral.ai/admin/monitor-comply/zero-data-retentionMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Regional inferenceID pd-11 | Product Documentationdocs.mistral.ai/inference/regional-inferenceMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only
Do you use my user data to train your models?ID pd-12 | Product Documentationhelp.mistral.ai/en/articles/347617-do-you-use-my-user-data-to-train-your-artificial-intelligence-modelsMistral AIOfficialNot counted (documentation)No date statedDocumentation checked Oct 25, 2026CurrentVerification only