Skip to main content
Mistral VibeProduct page

Mistral Vibe Signals

What engineering leaders and their teams report about Mistral Vibe, with every finding tied to its evidence.

Read the findings

What the evidence says

Whose sources count

Practitioner sentiment, all practitioners

+18 Mixed from 42 sources that take a side

How this figure is made

Mixed overall signal, net 18 points

From 39 authors in 41 discussions. Use a task pilot to measure accepted work and review time.

Analyzed
85 total sources
Top praise
Low Price for Daily Coding (10 of 10 sources) See praise evidence
Top concern
Harness Bugs and Stalls (19 of 20 sources) See concern evidence

Dec 2025 to Oct 2026.

73 sources from practitioners, by month and sentiment.

Across public accounts, low price and local models draw the most praise. The top concerns are output that trails Claude Code and Codex, and harness bugs, followed by plan limits that run out under heavy use.

Positive, mixed and negative sources

The score counts them as 18 positive, 10 mixed and 11 negative votes, one per author. See How the numbers work.

See the evidence

Below: 6 praise themes, 7 concerns, 3 close to agreement and 3 disagreements.

Findings

Counted for All practitioners, from 73 sources. Change group

What practitioners praise

Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.

  1. Low Price for Daily CodingAll 10 sources on it praise itA flat monthly plan, or cheap hosted models, that covers daily agent work for a fraction of what Claude costs.

    Counted for All practitioners.

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    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

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

    8. 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

    9. 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

    10. 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

    Open them in the record
  2. Solid Results on Scoped Tasks7 of 9 sources on it praise itChanges that work and follow the project's style when the task is clear and bounded.

    Counted for All practitioners.

    Positive, 7

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

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

    Mixed or negative, 2

    1. 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

    2. 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

    Open them in the record
  3. Clean, Contained Terminal Workflow7 of 10 sources on it praise itA minimal interface that stays in its directory, reads what it needs, and works with little setup.

    Counted for All practitioners.

    Positive, 7

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

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

    Mixed or negative, 3

    1. 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

    2. 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

    3. 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

    Open them in the record
  4. Runs on Local Open-Weight Models6 of 8 sources on it praise itPointing Vibe at Devstral Small, Qwen, gpt-oss, or another model on the developer's own hardware.

    Counted for All practitioners.

    Positive, 6

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

    Mixed or negative, 2

    1. 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

    2. 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

    Open them in the record
  5. Hosted GLM and Mistral ModelsAll 5 sources on it praise itAccess through one Mistral plan to hosted models such as GLM 5.2, GLM 5.3, and Mistral Large 4, with large context.

    Counted for All practitioners.

    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

    2. 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

    3. 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

    4. 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

    5. 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

    Open them in the record
  6. A European Vendor4 of 5 sources on it praise itChoosing Vibe because Mistral is a European company, for sovereignty, privacy, or to move off US providers.

    Counted for All practitioners.

    Positive, 4

    1. 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

    2. 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

    3. 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

    4. 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

    Mixed or negative, 1

    1. 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

    Open them in the record

What concerns them

Every concern practitioners raise, most raised first.

  1. Harness Bugs and Stalls19 of 20 sources on it raise it as a concernLoops, stalls, slowness, broken editor integrations, platform bugs, and regressions after updates.

    Counted for All practitioners.

    Raised as a concern, 19

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

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

    8. 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

    9. 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

    10. 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

    11. 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

    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

    13. 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

    14. 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

    15. 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

    16. 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

    17. 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

    18. 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

    19. 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

    Discussed without concern, 1

    1. 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

    Open them in the record
  2. Output Behind Claude Code and Codex13 of 16 sources on it raise it as a concernResults that trail Claude Code, Codex, or Gemini on complex, niche, or long tasks.

    Counted for All practitioners.

    Raised as a concern, 13

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

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

    8. 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

    9. 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

    10. 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

    11. 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

    12. 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

    13. 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

    Discussed without concern, 3

    1. 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

    2. 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

    3. 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

    Open them in the record
  3. Setup Beyond the Default PathAll 9 sources on it raise it as a concernTool-call errors, chat-template failures, and missing settings when Vibe runs on local servers, other models, or corporate networks.

    Counted for All practitioners.

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

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

    8. 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

    9. 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

    Open them in the record
  4. Telemetry, Training, and EU Routing DefaultsAll 6 sources on it raise it as a concernTelemetry, model training, commit signatures, and processing location that a user must change or cannot set.

    Counted for All practitioners.

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

    GILD's fact checks, which don't count as sources

    Checked Oct 25, 2026.Vibe's configuration sets enable_telemetry to true by default, Vibe input and output train Mistral's models unless a user opts out, and the EU regional endpoint is documented for the API. Configuration

    Open them in the record
  5. Context Limits and Compaction6 of 7 sources on it raise it as a concernContext windows that fill on real projects, and compaction that loses or fails to recover the session.

    Counted for All practitioners.

    Raised as a concern, 6

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

    Discussed without concern, 1

    1. 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

    Open them in the record
  6. Plan Limits That Run Out6 of 10 sources on it raise it as a concernMonthly usage that heavy users exhaust, rate limits that are hard to work out, and billing rules that differ by key.

    Counted for All practitioners.

    Raised as a concern, 6

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    6. 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

    Discussed without concern, 4

    1. 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

    2. 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

    3. 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

    4. 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

    GILD's fact checks, which don't count as sources

    Checked Oct 25, 2026.Mistral documents one monthly usage budget shared across Studio, the API, and Vibe Code. When it runs out, Vibe Code stops until the next period unless pay-as-you-go is on. API keys and profiles

    Open them in the record
  7. Approval Checks That MissAll 5 sources on it raise it as a concernPermission rules, plan mode, or approval checks that let the agent do more, or less, than configured.

    Counted for All practitioners.

    1. 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

    2. 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

    3. 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

    4. 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

    5. 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

    GILD's fact checks, which don't count as sources

    Checked Oct 25, 2026.Mistral describes smart-approve as a classifier with no sandbox isolation. It reserves auto-approve for disposable environments and lets an administrator disable auto-approve; a bash allowlist replaces the default list. Safety, approvals, and permissions

    Open them in the record

Where the evidence agrees

Statements this group's sources agree on, then the ones close to agreement.

Close to agreement: each needs 15 supporting sources

  1. Below threshold

    Vibe handles small, well-scoped changes a developer watches closely, and falls short on large or long-running tasks.

    6 supporting sources, 1 contradicting
  2. Below threshold

    Many users try Vibe because Mistral is European, then judge it on whether the work holds up against US agents.

    5 supporting sources
  3. Below threshold

    Mistral's hosted GLM 5.2 and 5.3 made Vibe markedly more useful for the users who switched to them.

    5 supporting sources, 1 contradicting

Where it disagrees

Questions the sources split on, with the count on each side.

  • Evidence remains mixed

    Is Vibe close enough to Claude Code to use in its place?

    • Close enough, 6 sources

      Some measure or find little difference on their work, or prefer Vibe's harness, and reach for Claude only when Vibe falls short.

    • Clearly behind, 6 sources

      Others found Vibe's output and tool handling well behind Claude Code on the tasks that matter to them.

  • Evidence remains mixed

    Do local models work well in Vibe?

    • Works locally, 6 sources

      Some run Devstral Small, Qwen, or gpt-oss in Vibe and get working changes with little setup.

    • Struggles locally, 4 sources

      Others hit tool-call errors, lost history, or context that fills on small projects.

  • Evidence remains mixed

    Does a Vibe plan cover heavy daily use?

    • Covers it, 4 sources

      Some have not hit a limit and call the monthly plan generous for the price.

    • Runs out, 5 sources

      Others used up a plan in days or hours, or hit rate limits they could not explain.

The evidence

Whose experience this is

The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.

Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 1 accounts; GILD prints their sentiment from 20.

  • Engineering leaders and teams

    4 sources. These accounts focus on plan usage across a team, approval and permission controls, data handling, and security review.

  • Individual builders

    69 sources. These accounts focus on price, local and hosted model choice, output quality against Claude Code, and day-to-day reliability.

  • All practitioners

    73 sources. This count includes everyone: individual builders and the four team accounts together.

73 sources from practitioners, by the context they work in. Filled rows count for this group.

  1. Individual practitionerSolo developers and independent builders69 sources, counted here

    Emphasizes Price, local and hosted models, and quality against Claude Code

  2. Very small team2 to 10 engineers, or a team of unstated size1 sources, counted here

    Emphasizes How a shared Team plan's limits work

  3. Professional team11 to 50 engineers, or a named company's team3 sources, counted here

    Emphasizes Shell permission checks under security review

  4. Technical leadershipLeaders setting adoption across teamsNo sources from this setting yet
  5. Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet

What changes with scale. Individual builders judge Vibe on price, model choice, and how close it comes to Claude Code. The team accounts focus on usage limits, administrator control of training, and whether the approval check matches what the shell actually runs.

Where the sources come from

Where this group's sources were published.

Counted for All practitioners, from 73 sources. Change group

85 sources for this group, 12 of them documentation

  • Developer Communities69, 81% of 85 sources
  • Product Documentation12, 14% of 85 sources
  • Engineering Blogs & Studies4, 5% of 85 sources

Older evidence is retained when it still applies. Sources tied to Devstral 2 stay in the record because users still run it locally; closed bugs and fixed vulnerabilities stay in the history, marked Needs a recheck.

See sources by origin

The record

Who each source is, how it knows, whether it still applies and what it counts toward.

Newest first, on its own page. Every count above opens its sources there.

Read all 85 sources

About this read

What changed, and how we count

What changed

  • Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Mistral Vibe now casts no vote; it still counts toward its topics and is listed, and 26 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders move from +15 to +18 and all practitioners from +13 to +18.
  • Oct 31, 2026: rewrote 5 summaries that two blind coders found overstated their sources, so each says what its source says. Two GitHub issues state no view of Vibe overall and now carry no sentiment, and a failed MCP install that faults the harness as well as the model no longer contradicts the harness-limits statement. Individual builders move from +15 to +16 and all practitioners from +11 to +12.
  • Builds the first Mistral Vibe evidence base from public sources only. Every source links to the page it comes from, names its author and publication date, and carries the exact words it is coded from.
  • Shows a finding for a group only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
  • Counts a GitHub issue as mixed unless its author rejects or abandons Vibe, and keeps reports that only discuss Devstral models outside the record unless they used Vibe.
  • Leaves sentiment unset where a source gives no opinion of its own use, such as a question about EU routing or an expectation before real use.

Method

A running review of what engineering teams report about Mistral Vibe, from individual builders to professional teams. Each finding links to its sources, and each conflict shows both sides.

Counts cover only the sources GILD reviewed.

Who counts

Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups

Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.

How the numbers work

  • Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
  • Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +12 mixed (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
  • Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Weighted, it read +11 Mixed; with one vote per author it read +12 Mixed. No evidence changed.
  • Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +13 Mixed and now reads +18 Mixed.
  • Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
  • Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
  • Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
  • Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
  • Disagreements. The count on each side. GILD names no winner and gives no share of all users.
  • Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.

Labels on a source

A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.

Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.

Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 1, individual builders 5 of 41, all practitioners 5 of 42.

Limits

  • These figures describe reviewed sources. They do not represent all Vibe users. GILD searched Hacker News through its API, r/MistralAI, r/LocalLLaMA, r/ChatGPTCoding, and r/vibecoding through an archive, issues on mistralai/mistral-vibe, and the web for blogs. Lobsters had no Vibe discussion, and several other subreddits were rate-limited. Four sources speak for a team: a security firm's review, one developer on a two-user Team plan, and two comments from a Team-plan administrator about training controls. The r/MistralAI community draws Mistral's own users, which can tilt its share toward people already on a plan.
  • Vibe moved from Devstral 2 to Mistral Medium 3.5 as its default model in May 2026, and Mistral added hosted GLM models and Mistral Large 4 after that. Sources record the model inconsistently, and each shows what it states. Bug reports Mistral has since closed and the fixed permission bypass are marked Needs a recheck.

Every count, and the sources behind it

22 findings for 3 groups

Each row opens its sources for the group you are reading.

FindingEngineering leaders and teamsIndividual buildersAll practitionersSources
Current readCurrent sentiment0 positive, 1 mixed, 0 negative19 positive, 11 mixed, 11 negative19 positive, 12 mixed, 11 negativeSources
PraiseSolid Results on Scoped Tasks0 of 0 positive (under the minimum)7 of 9 positive7 of 9 positiveSources
PraiseLow Price for Daily Coding0 of 0 positive (under the minimum)10 of 10 positive10 of 10 positiveSources
PraiseRuns on Local Open-Weight Models0 of 0 positive (under the minimum)6 of 8 positive6 of 8 positiveSources
PraiseClean, Contained Terminal Workflow0 of 0 positive (under the minimum)7 of 10 positive7 of 10 positiveSources
PraiseA European Vendor0 of 0 positive (under the minimum)4 of 5 positive4 of 5 positiveSources
PraiseHosted GLM and Mistral Models0 of 0 positive (under the minimum)5 of 5 positive5 of 5 positiveSources
ConcernOutput Behind Claude Code and Codex0 of 0 raise it (under the minimum)13 of 16 raise it13 of 16 raise itSources
ConcernHarness Bugs and Stalls0 of 0 raise it (under the minimum)19 of 20 raise it19 of 20 raise itSources
ConcernPlan Limits That Run Out1 of 1 raise it (under the minimum)5 of 9 raise it6 of 10 raise itSources
ConcernContext Limits and Compaction0 of 0 raise it (under the minimum)6 of 7 raise it6 of 7 raise itSources
ConcernSetup Beyond the Default Path0 of 0 raise it (under the minimum)9 of 9 raise it9 of 9 raise itSources
ConcernApproval Checks That Miss1 of 1 raise it (under the minimum)4 of 4 raise it (under the minimum)5 of 5 raise itSources
ConcernTelemetry, Training, and EU Routing Defaults2 of 2 raise it (under the minimum)4 of 4 raise it (under the minimum)6 of 6 raise itSources
ConsensusGood for scoped, watched work0 supporting (under the minimum)6 supporting, 1 contradicting (below threshold)6 supporting, 1 contradicting (below threshold)Sources
ConsensusEurope is why people try it0 supporting (under the minimum)5 supporting (below threshold)5 supporting (below threshold)Sources
ConsensusHosted GLM changed the result0 supporting (under the minimum)5 supporting, 1 contradicting (below threshold)5 supporting, 1 contradicting (below threshold)Sources
ConsensusThe harness holds it back0 supporting (under the minimum)3 supporting, 2 contradicting (under the minimum)3 supporting, 2 contradicting (under the minimum)Sources
DisagreementIs Vibe close enough to Claude Code to use in its place?Close enough 0, Clearly behind 0 (under the minimum)Close enough 6, Clearly behind 6Close enough 6, Clearly behind 6Sources
DisagreementDo local models work well in Vibe?Works locally 0, Struggles locally 0 (under the minimum)Works locally 6, Struggles locally 4Works locally 6, Struggles locally 4Sources
DisagreementDoes a Vibe plan cover heavy daily use?Covers it 0, Runs out 1 (under the minimum)Covers it 4, Runs out 4Covers it 4, Runs out 5Sources
Current readEvidence mix16 sources81 sources85 sourcesSources

Fact checks

GILD's checks of claims against official documentation, kept apart from the source counts.

  • Plan Limits That Run Out. Mistral documents one monthly usage budget shared across Studio, the API, and Vibe Code. When it runs out, Vibe Code stops until the next period unless pay-as-you-go is on. API keys and profiles, checked Oct 25, 2026
  • Approval Checks That Miss. Mistral describes smart-approve as a classifier with no sandbox isolation. It reserves auto-approve for disposable environments and lets an administrator disable auto-approve; a bash allowlist replaces the default list. Safety, approvals, and permissions, checked Oct 25, 2026
  • Telemetry, Training, and EU Routing Defaults. Vibe's configuration sets enable_telemetry to true by default, Vibe input and output train Mistral's models unless a user opts out, and the EU regional endpoint is documented for the API. Configuration, checked Oct 25, 2026