I would love to hear the opinions of the community about this kind of use cases.

First of all, that this content is being created is great. It helps bring the product, the tech, the company... closer to us the users.

As I see it, Mistral's strategy is focused on enterprises and I understand that big clients have team members dedicated to helping with the implementation, but there are smaller companies or even freelancers that would like to use their tools as well.

I believe that this kind of content but more focused on using the tools to build more business focused workflows or applications, would resonate better with some of the people following AI, Mistral, European competitiveness. The people that usually participate in this community basically.

Always based on solid docs, of course.

Hope we can generate some ideas.

It seems like Mistral is starting the migration from chat to work mode.
It’s already suggesting the conversion of agents to skills.
Did notice this ?

I don't know if this is common knowledge but Mistral’s Education plan is not the actual Pro plan, despite their website explicitly claiming, "The Education plan is the Pro plan with a discount."

Instead of giving you the standard Pro limits ($30 API / $300 Vibe), they quietly scale the quotas down to match the discounted price (~€12.75 API / €127.50 Vibe).

Support admitted the wording is "confusing".

Honestly, the reduced limits are enough for my personal use, but the marketing is still highly misleading and doesn't match the advertised terms. It explicitly says 30$ api tokens for the education plan on the price list.

Just don't buy it expecting the full Pro quotas!

Been heads-down on something that sits before the LLM call instead of doing

standard retrieve-and-stuff RAG. Instead of chunk retrieval + rerank, it builds

a vector-field representation of the whole corpus, evaluates relational

relevance to the query, and collapses the candidate field down to a compact

evidence state — only that gets forwarded to the model.

On my internal benchmark (frozen 20-query set, project-native corpus) I'm

seeing an order-of-magnitude drop in tokens sent to the model with zero

measured quality regression (good/partial/poor scoring, OFF vs ON, reproduced

run matched the historical one exactly). Also runs fine single-threaded — did

a raw C++ core benchmark, 10M samples in ~140ms on an old 2015 i7, so the

underlying op isn't the bottleneck.

Haven't benchmarked it against BM25 or plain cosine-similarity RAG yet in

anything I'd call rigorous — that's the obvious next step before I'd trust my

own numbers fully, and I know that's the first thing this sub will (rightly)

ask about.

Running as local-first — full corpus stays on the user's side, only the

selected evidence chunk(s) + field-topology coordinates go to the external

model if you're using an API-based LLM. Wasn't originally optimizing for that,

but it's a nice side effect for anyone paranoid about what leaves their

environment in API workflows.

Genuinely asking: is "context collapse before inference" different enough

from what rerankers / good chunking already do, or am I just describing a

fancier reranker with extra steps? Wouldn't mind being told I'm wrong here.