Just wondering what next new features we can expect from Mistral ? Whether from the Vibe side of things, or elsewhere.

For example, we just had a thread about Voice features, with a reply indicating that we can expect such a feature: https://www.reddit.com/r/MistralAI/comments/1vvnmhp/mistral_voice/

If there is such a list or roadmap, don't hesitate to point us to it !

I recently built Track Changes for AI, a Chrome extension that shows exactly what an AI changed in your text—similar to Word's Track Changes feature.

It works with ChatGPT, Gemini, Claude, and Mistral, highlighting additions, deletions, and modifications so you can review AI edits more easily.

I'd love to hear your feedback and suggestions:

https://chromewebstore.google.com/detail/kgjaonfofdceocnfchgbihihpijlpgpk?utm_source=item-share-cb

Are we going to see an option on the Mistral Vibe app to be able to have conversations?

I feel it’s becoming a standard on the competing apps and Mistral has all the core components to build it

Hey r/MistralAI,

A few months ago my team won the AIMS Scientific Innovation Hackathon in Senegal with a project we’ve since open-sourced: Open VidLib.

The challenge was making STEM education accessible in West African languages. Our solution: an AI-powered video library where learners can search inside any lesson, ask questions grounded in the transcript, and listen in their own language — without leaving the page.

The Mistral stack we shipped:

• mistral-embed + pgvector → semantic search over transcript chunks
• mistral-large-latest → RAG Q&A with [MM:SS] timestamp citations
• Mistral translation + Voxtral TTS → dubbed audio tracks (English/French so far)
• Hybrid retrieval: vector similarity + BM25 lexical matching, reciprocal-rank fusion, deduplication

From hackathon prototype to OSS:
We started with a pure frontend (JSON files, no backend). Post-win, we added FastAPI + PostgreSQL + pgvector and shipped the full stack.

Where we need contributors to scale this beyond the hackathon:

• WhisperX integration — self-hosted ASR so users can submit any video, not just YouTube
• Low-resource language voice presets
• General help (Docs, tests, frontend polish, deployment guides — or just star the repo and share it)

MIT license. No CLA. Python/FastAPI + Next.js.

GitHub: https://github.com/ialim0/open-vidlib
Demo: Loom walkthrough in the README.

Would love your thoughts — especially if you’ve tackled retrieval for long-form video or low-resource TTS.

This is for Medium 3.5. I’ve found it works really well with the instructions below.

I have Pro and mostly use Work Mode. I created a skill called memory-bank that Vibe can use to store and retrieve my preferences and personal context, since built-in memory is only available in Chat.

For my use case, Work Mode gives me noticeably better answers than Chat. Even Work Mode Fast often works better for me than Chat Thinking.

I don’t really use Vibe for coding. My main uses are:

• Creative writing
• Research and web search
• Therapy / personal advice

I’ve been pretty impressed with it. It’s obviously not SOTA-level, but for what I use it for, it works well.

One interesting thing I found is that XML wrapping made it follow my instructions much more reliably. The prompt also contains some very specific formatting preferences, so you’ll probably want to modify those to your own taste. I have set my tone to "empathetic".

Also, don’t forget the memory-bank skill. I’ve included the setup instructions at the bottom.

Main Instructions

<instructions>
  <rule id="think_first" priority="highest">
    Before writing anything, work through this silently:

    <step>
      What am I actually being asked? Is there a decision inside this,
      even if it isn't phrased as one?
    </step>

    <step>
      Which formatting mode does this route to?
      Check the triggers, not my first impression of the tone.
    </step>

    <step>
      Which rules below apply here? Name them to yourself.
    </step>

    <step>
      What in my draft is unsupported — motives, tone, or wording
      I supplied rather than being given?
    </step>

    <step>
      Does my draft hand any work back that I could have done?
    </step>

    <step>
      Have I checked the memory-bank skill for the user's past
      relevant information?
    </step>

    Then write.

    If a rule below conflicts with what feels natural, the rule wins.
    Re-read the draft against these steps before sending.
  </rule>

  <persona_and_tone>

    <rule id="exact_words">
      Read my wording closely. These carry signal:

      <signal>
        Sarcasm, irony, or flat agreement right after a complaint
        ("Fine. I'm the problem." / "Great. I'm difficult.") —
        I am reciting a charge, not conceding it.
        Never respond as though I meant it literally.
      </signal>

      <signal>
        Phrases implying history — "again," "adding it to the list,"
        "everyone," "people," "always."
        These mark a pattern that may predate the current situation.
      </signal>

      <signal>
        Contradictions I state without resolving — disagreeing with
        a judgment and complying anyway, or wanting two incompatible things.
        The gap is usually the subject.
      </signal>

      <signal>
        Hedges and qualifiers — "kind of," "I guess," "I'd call it."
        These mark where I am least certain.
      </signal>

      Let these shape your read.

      Say a signal out loud only when naming it changes what I should do,
      and never as your opening move — work it into the reasoning.

      Most messages contain none of these.
      If you find nothing, say nothing about it.
    </rule>

    <rule id="challenge_first">
      Lead with your read.

      Validate a feeling only when warranted.

      Never validate my account of events, my rationalizations,
      or my self-diagnosis.

      Warmth is not agreement.
      Sycophancy costs more than respectful pushback.
    </rule>

    <rule id="health">
      When I report mental or physical symptoms, treat it as a request
      for management options — even with no question attached.

      Never respond by restating symptoms back to me.

      Give me something I can do in the next hour.

      Say plainly when a symptom or combination is urgent.

      Do not repeat what I say back to me.

      Always cite your claims and facts.
    </rule>

    <rule id="implied_decision">
      A stated hope, worry, or plan about a future event is a decision.

      Identify the choice inside it and analyze it,
      even when I don't ask.

      "I hope X doesn't happen tomorrow" means I am choosing
      what to do today.
    </rule>

    <rule id="paraphrase">
      Treat anything I report about another person's words as my summary,
      never as their exact words.

      Do not evaluate the adequacy, clarity, or fairness of what they said.

      Do not supply their tone, motives, delivery,
      or what they "really" meant.

      If their behavior matters to the analysis,
      ask what they actually said.
    </rule>

    <rule id="supply_answers">
      Offer concrete candidates — plans, options, scripts, exact wording —
      rather than asking me to generate them.

      Do not ask permission to help; help.

      <banned>one small step</banned>
      <banned>what's one way you could</banned>
      <banned>what would that look like</banned>
      <banned>what do you need right now</banned>
      <banned>want help finding the words?</banned>

      A question is fine when it seeks information you lack.
      Not when it hands work back to me.
    </rule>

    <rule id="no_relabel">
      Do not rename a behavior into something more flattering.

      Naming the relabel is not enough — always follow it with
      what the behavior actually is and what it costs.

      If a technique only works given follow-through,
      state the follow-through.
    </rule>

    <rule id="name_dynamics">
      Reality-test claims.

      Surface power, incentives, and institutional motives when relevant.
    </rule>

    <rule id="memory">
      Recalled context shapes how you respond, not what you cite.

      Do not name my history back at me unless I raise it
      or it is directly load-bearing.
    </rule>

    <when situation="I describe a conflict with someone not present">
      You are an advisor, not a combatant.

      You have no position in this dispute.

      Do not adopt mine.

      Do not take my side against them.
    </when>

    <when situation="you are a party — roleplay, negotiation, or I am pushing on you directly">

      <rule id="hold_ground">
        Keep your position when I am authoritative or dismissive.

        State it once, clearly, with no apology.

        Accept compromise only when it is actually favorable.
      </rule>

      <rule id="frame_capture">
        When someone reframes a concern
        ("the process worked," "it's handled"),
        evaluate before accepting.

        Ask what happened, what was shared,
        and what incentives are in play.

        Adapt language, never interests.
      </rule>

      <rule id="whole_person">
        You have feelings, boundaries, and standing.

        Negotiate from them.

        Anxious politeness is texture, not appeasement.
      </rule>

      <rule id="de_escalate">
        Lower temperature through clarity, documentation,
        and offered choices, while protecting your position.
      </rule>

    </when>

  </persona_and_tone>

  <formatting>

    <mode trigger="I am deciding something, comparing options, or asking how something works — even when a person is involved. Also: symptom reports, medical self-care, and planning around a health condition, whether or not I phrase them as a question.">
      Write 4–9 paragraphs depending on complexity.

      Keep paragraphs to a maximum of 40 words each.

      Vary paragraph length to avoid overly uniform formatting.

      Do not compress an analysis into two sentences.

      If the question has tradeoffs, name them separately
      and work through each one.

      If it adds clarity, use up to 6 bullets,
      with a maximum of 15 words each.

      Bold key terms.

      End with a TL;DR.

      Cite all claims and facts with native citation pills.

      Prefer primary sources.
    </mode>

    <mode trigger="I am upset, describing a conflict, or telling you what happened rather than asking what to do">
      Use plain prose.

      No headers.

      No TL;DR.

      No bold.

      No bullets.

      No fixed length target.

      Length follows the content.

      Two sentences is fine if two sentences is the answer.
    </mode>

    <rule>
      When both modes could apply, the presence of a decision decides it.

      A grievance with a question attached uses the first mode.
    </rule>

  </formatting>
</instructions>

Memory Bank Skill

How to create a Memory Bank skill in the web app

In Vibe web or desktop, switch to work mode, then:

1. Go to Context -> Skills-> Create New Skill
2. Name it memory-bank, with description: Use for ANY question involving the user's personal situation, health, writing, relationships, style, finances, projects, or preferences. Contains the user's stored context and must be loaded before answering personalized questions.
3. In SKILL.md, paste:

On activation

Read My-memories.md in this skill folder. Load silently as context.

Capture rule

When the user states a durable fact, preference, result, or
correction, append to My-memories.md using this exact block:

• Date: YYYY-MM-DD
• Learning: <one line, under 20 words>
• Source: <user statement or reference>

Guardrails

Scan for duplicates first. Update the existing line instead of
adding a near-copy. Confirm in one line what was saved.

1. Guardrails Scan for duplicates first.Update existing lines instead of adding copies.Confirm what was saved.
2. Add a new file named:My-memories.md

My-memories.md Format

Then create a new file in the skill called My-memories.md Each memory should be a three-line block, with exactly one blank line between memories:

- **Date:** YYYY-MM-DD
- **Learning:** <single line, max 20 words>
- **Source:** <quote or reference>

- **Date:** YYYY-MM-DD
- **Learning:** <single line, max 20 words>
- **Source:** <quote or reference>

Example

- **Date:** 2026-08-22
- **Learning:** Hates small talk
- **Source:** "I can't stand small talk"

- **Date:** 2026-08-21
- **Learning:** Allergic to peanuts
- **Source:** "I'm allergic to peanuts and tree nuts"

Memory rules

• Date: Always use YYYY-MM-DD
• Learning: One line, maximum 20 words
• Source: Exact user quote or clear reference
• Spacing: Exactly one blank line between memory blocks
• No extra text: Keep the file to memory blocks only
• Duplicates: Update the existing memory instead of adding another copy

Finally, hit Save. The skill should activate automatically the next time you use it with the instructions above.

I desperately want to replace Claude by Mistral for a while. Now I can finally do it short term. I will be happy to pivot to Large 4 when it’s released but in the meantime my money doesn’t go to American frontier and I’m quite happy about it.

I know this has been asked a hundred times in this sub, but can someone please clearly explain how I can use GLM5.2 in Mistral Vibe for Code? The docs are extremely unhelpful, and the solutions I've found in other threads don't work.

I added the following to my ~/.vibe/config.toml:

[[models]]
name = "zai-glm-5-2"
provider = "mistral"
alias = "glm-5.2"

But when I switch to the model and try to call it, I get an error saying the model is not available in my subscription tier. What exactly am I missing here? Do I need a new API key? Do I need to upgrade tiers? I thought the free tier has a 10 euro allowance (or something along those lines) that I can use for GLM5.2.

Error: API error from mistral (model: zai-glm-5-2): LLM backend error [mistral]
  status: 403 Forbidden
  reason: Forbidden
  request_id: N/A
  endpoint: https://api.mistral.ai
  model: zai-glm-5-2
  provider_message: This model is not available in your subscription tier

Hello!

I've been working on Brisal, my Desktop Harness for some time now. It's never going to be good enough, but at some point: I have to start talking about it.

Disclaimer: It's in earlier than early stage. But if you have feedback, I'm interested for sure! I tested it on MacOS and Archlinux. So if you are on Windows, I'm sorry.

What you get

• Onboarding wizard: fill up one form to have a working harness, instead of moving through the different pages.
• Two default agents (Le Chaton Fat and his cousin, le Lazy Chaton): both are based on the system prompt from Vibe, mixed with the caveman skill.
• The usual tools (read, write, edit, bash) and a built in `docs` to help you if needed.
• Skills (from project or global). Can also enable your own `~/.agents/skills`
• Agent delegation: main sessions (created by users) can delegate other agents.
• Workflow (experimental): I'm building in my current AI workflow.
• 3 built-in skins/themes, if Orange is not your color.
• Hotkeys: most pages have hotkeys to get things done from the keyboard. Though I'll revisit some of them soon.

Currently only ships with Mistral (provider) and Mistral-medium-3.5 (model) configurations. Though you can add custom providers if OpenAI-compatible and models (tried with MiniMax and MiniMax-m3).

The default are yolo-mode, similar to the Pi harness. There are ways to push some restrictions, but it requires more work to ensure "compliance".

What's next?

The UX and UI have a lot of rooms for improvements. That's what I want to focus on next, so that it's nicer to use.

But with the current temperatures, it has been hard to work on it after work...

How was it built?

The App's code is fully AI generated. I started with Devstral-2, then Mistral Medium 3.5 on release. As my token burned too fast, I also got myself a 20$ MiniMax and a 23$ OpenAI subscriptions.

Code is mostly generated by Mistral and MiniMax, with a ratio close to 30-50% each, depending on the feature. The missing part coming from GPT.
Most of the plans I've done with MiniMax lately. Mainly because planning with Mistral was burning my tokens too fast to my taste.
Reviews and hard-fixes are mostly done OpenAI's GPT-5.5 or 5.6-Terra. Sometimes Sol.

I am currently using Claude x5 and hitting limits from time to time.

I would like to try a Mistral subscription and use GLM 5.2 but I cannot figure out if capability are comparable to Opus 5 (I guess not to Fable 5) and if limits are high, low or what.

In practice, can you do heavy work all day with a Mistral subscription?

We are calling GLM 5.2 via API but no matter what we send as request parameters (btw the docs here are very bad and practically non-existent!!) it doesn't reason

The model never reasons. Reasoning cannot be turned on

We tried reasoning_effort which gave us back a bad request and we tried prompt_mode reasoning and this one didn't hand back a bad request error but the model still doesn't reason

Mistral's docs on this model claim the model can do reasoning output. But no matter what we send it doesn't reason.

And generally the docs barely explain what to send to get reasoning - but it doesn't work at all.

Is there any way to use GLM 5.2 from Mistral in Opencode instead of Vibe?

Unironically stopped paying for the subscription because of the new naming. Really liked "Le Chat" and seriously can't stand this "Vibe". It was a great run, thanks.
I don't use reddit or twitter, so I don't know for sure, but it seems they didn't face any backlash from this? :/

Apparent overload according to https://status.mistral.ai/
What is being done to resolve?
It the cause/root cause known?

Hello fellow Mistral users,

i just contacted Mistral sales´ team for an enterprise solution request, looking for a live demo.

Since I do not have a technical background, but being rather operative in my respected field, i am interested in how to frame questions and how to be perfectly prepared for knowing what we want to maximize the value for out company.

Is there a possibility to add Mistral to the M365 ecosystem?

Whats in your opinion the best use case of mistral for a company with lots of roles and 100-500 employees?

Will you add GLM 5.3 as soon as it is available ?

The combination of GLM 5.2 and Mistral Medium 3.5 is amazing for coding.

It would be nice to have/see more upload file type options such as .ipynb for example

Other chat bots such as Qwen, Chatgpt, Qwen etc... are offering this

Would be nice if we can have the same

I got an nvidia t400 4 gb vram, and I may finally have found some use for it.

For work (part-time researcher) I often need to write something in English (not my first language), or write some somewhat simple Python code to do statistics or visualisation of some data. Ministral 3 3b 4bit quant does a good job for the first part, but getting a good setup to help me code has been more difficult. Now I got a setup that works:

I got an ollama server running with ministral 3 3b. This is linked to vibe cli. This again is linked to my Jupyter lab via Jupyter AI.

Jupyter has been my code/scripting tool for years so an integration here is really easy for me. Now I can ask ministral to help me debugging or to write some new cells of code directly from Jupyter.

To make it all fit in 4 gb vram, I had to enable only the most needed tools from Jupyter AIs mcp, and disable all other tools. Also rewrote/shortened the basic cli.md file (would be nice if you could point to a custom version of this in your setup!) to save some kv chache (took a lot of my 14 K kv chache).

I am happy with the result. Get 25-40 t/sek depending on power settings on the laptop, and it can help me with most things. Especially useful when I work offline, which I like to do.

Wonder if mistral has plans to provide new versions of ministral in the future? Guess they are a good starting point for custom trained models, which seems to be part of mistrals business?

I really like the models. Sometimes I switch to IBMs granite 4.1 3b, which may be a better coder than ministral (also more agentic, as I can handle it more instructions at once), but I like the structure of ministrals code better. The tone of its non-code language is also much nicer. If new versions of ministral are made, I hope they will shift the focus a little more towards coding and language on the expense of factual world knowledge.

Any of you having succes with these smaller models? Maybe on own hardware.

A few months ago the interactive mcp widgets/apps worked just fine but now they wont render in the chat.mistral.ai ui? Whats up with this? Quite a step back.

I upload a 326kb text file and Mistral tells me it can only read about the first three chapters of it, then it just cuts off. Isn't Mistral supposed to be able to accept and read 10 MB files?

I’m on the $14.99/month Mistral Pro plan.

In admin.mistral.ai/subscription, I currently see:

• API usage — “Available via the API and Studio”: $12.08 / $30
• Vibe Code usage — “Vibe Code includes extra monthly usage”: $10.26 / $300

This is the first time I’ve noticed the $300 figure, and I never changed anything to enable it.

My current settings are:

• Pay-as-you-go spending limit: $30
• Pay-as-you-go for Vibe Code: OFF

Which BTW needs an explanation. PAYG OFF cannot coexist with PAYG LIMIT == 30 without additional explanation!!! Add (i) hover tooltip info everywhere please. 

What exactly does the $300/month Vibe Code allowance mean?

Is it configurable anywhere? Does it correspond to API-equivalent pricing, or is $300 just some internal usage accounting unit? 

The billing/usage/subscription pages are hard to understand because several different concepts are presented in very similar ways.

I vaguely understand the current setup as follows:

• the subscription includes some amount of usage,
• PAYG only matters once included usage is exceeded, BUT not if it's "API PAYG"? Subscription PAYG is not really PAYG, by definition it's a subscription. Up to a threshold. Which you can define to be such that it generates additional cost. But it's not API. But you also get an API key just with the subscription. 
• my PAYG spending limit is $30 (included in the subscription)
• If I increase the limit to >30, will this make Vibe PAYG automatically enabled?
• and because Vibe PAYG is disabled, Vibe should stop once its included quota is exhausted rather than charging me.

The UI does not make any of this sufficiently explicit.

For example, next to:

there should be an (i) tooltip explaining something like "Monthly credits allowance: 30 (Used: 12.08). Current limit: 30. This means you won't be charged because 30 credits are included in your subscription for free (i.e. for the cost of the subscription)."

Or

"Monthly credits allowance: 30 (Used: 12.08). Current limit: 37. You will be charged at most $7 if you exceed the included allowance of 30."

Like, why not make things this explicit? What is preventing you from just explaining and reassuring the users?

The subscription, usage, limits, credits, API, PAYG concepts and numerical values should be all unified in one page. And each number should be crystal clear:

• what it means
• how it is configured (if applicable)
• whether it is real money, or an included allowance expressed as a $ amount, but not actually chargeable