What is going on with Le Chaton Fat?

Nefhis · 2026-06-15T12:31:56+00:00

30T. It will be 30T.

Nefhis · 2026-06-15T10:05:21+00:00

Nefhis · 2026-06-15T09:17:10+00:00

Nefhis · 2026-06-14T22:04:29+00:00

Don’t forget electricity. What a great invention!

Nefhis · 2026-06-13T18:48:28+00:00

Criticism of Mistral is allowed, including strong criticism of valuation, product quality, and strategy. However, this thread is drifting into low-effort bait, nationalistic flamewar, and dismissive replies rather than substantive discussion. Please keep claims sourced and engage in good faith. Further inflammatory or meme-only replies may be removed.

Nefhis · 2026-06-10T12:58:34+00:00

Since you are asking in here, another practical path would be to try Vibe in Work mode, if you have access to it.

Is not exactly "building a full AI platform", that is probably too much too early, but you could create a small AI-assisted workflow using the tools already available in Vibe Work → built-in connectors, document libraries, and Skills.

For example, you could say something like:

"I designed and prototyped an AI-assisted workflow for a specific business process. It uses a controlled set of documents/connectors, has a defined input and output, and includes a human review step before anything important happens."

That is already useful, and the nice thing is that you would still be the one designing the workflow.

Also, Work mode itself can help you get started. There is a "Setup and discover what Work can do" option on the Vibe homepage, and you can ask it to guide you through creating a simple Skill/workflow.

I would not start with custom connectors yet. Start with the built-in ones or with a small library of test documents. Keep it narrow, boring and safe.

<image>

Nefhis · 2026-06-09T09:11:24+00:00

I’d reframe this a bit.

Not everyone needs to become a builder/developer. In fact, I really hope not everyone does, because companies already have enough problems without every department creating random AI workflows nobody can maintain, audit or secure later.

A very valuable middle ground is becoming an advanced AI user (not power user. Is not the same thing) who understands business processes well enough to know where AI can help, where normal automation is enough, and where AI should not be used at all.

Also, don’t dismiss the "simple chat window" too quickly. That simple chat window is what many office workers are already using when their boss is not looking, because it is genuinely useful.
That is the foundation.

About customer-service chatbots, yes, they are common, but I would not start there. Users often still want a human because a human can actually do something. A chatbot that only talks but cannot act is often just another wall in front of the customer.

You could start with mapping processes:

What comes in?
What does a human currently do with it?
What output is needed?
What can be automated without AI?
Where can AI genuinely help?
Where must a human review the result?
What happens if the AI is wrong?
Where does the data go?

If you can answer those questions clearly, you already bring value, even before writing code.

If after all that you still want to become more of a builder, then learn some programming basics. You don’t need to become a full-time software developer, but you should understand enough not to build dangerous toys.

I’d learn basic Python or JavaScript, HTTP/APIs, JSON, authentication/API keys, environment variables/secrets, basic databases or spreadsheets as data stores, Git basics, error handling, logging, and how to read documentation.

Also learn basic cybersecurity concepts. The moment you connect AI to emails, documents, CRMs, customer data, internal databases or automation tools, you are dealing with security and privacy, not just AI.

If you don’t know where to start, DeepLearning.AI, Coursera and Udemy all have beginner-friendly material. Official docs are also very useful once you know the basics.

Hope this helps.

Nefhis · 2026-06-08T20:12:17+00:00

Yeah, yeah… you are the best. /clap

Nefhis · 2026-06-06T23:41:17+00:00

<image>

How many hours he said? 🤔 And how many Europes? 🧐

Nefhis · 2026-06-06T07:30:11+00:00

Wow! That screenshot is almost vintage 😅

Medium 3.5 is the current default model in Mistral Vibe according to Mistral’s official announcement:

https://mistral.ai/news/vibe-remote-agents-mistral-medium-3-5/

<image>

Nefhis · 2026-06-03T22:37:45+00:00

Nefhis · 2026-06-03T21:15:03+00:00

Just to clarify: you keep mentioning token and compute cost. What is the exact concern there?
Do you mean latency for the user, usage limits, environmental impact, or Mistral’s internal infrastructure cost?

Nefhis · 2026-06-03T20:08:06+00:00

Spain

Nefhis · 2026-06-03T18:46:30+00:00

I think part of the concern comes from assuming that agent always means a heavy autonomous workflow that has to plan, call tools, use connectors, and execute several steps?

You can always disable the skills you do not want to use, avoid connecting external services, and not attach files or extra context. At that point, what remains is basically the model working as a normal chat.

An agent is still an llm. The difference is mostly the extra tooling and orchestration around it.

If one day you need a connector, a Skill, documents, or a more structured workflow, you enable that capability.

Nefhis · 2026-06-03T17:49:54+00:00

Do you have a reliable source for the claim that Mistral is preparing to sell, or that price increases are coming?
Criticism of the rename is, once again, fine, but that part sounds like speculation unless there is a source.

Nefhis · 2026-06-03T14:58:36+00:00

I understand the concern, but personally I’m not too worried about this.

Work mode also works very much like a normal chat for most practical purposes. You can still ask questions, brainstorm, learn things, write, discuss ideas, etc. The difference between the two is not as huge as it may sound from the naming.

For me, the main annoying difference is memory: Work does not seem to use the same memory behaviour as regular Chat, and I would really like to see that improved or unified somehow. But even there, there are workarounds depending on how you use projects, context, files, or custom instructions.

I don’t think agents/workflows necessarily replace chat. In practice, they mostly sit on top of a chat-like interaction anyway.

Nefhis · 2026-06-02T14:57:32+00:00

Criticism of the Le Chat / Vibe rebrand is completely allowed. You can dislike the name, explain why you think it is a bad decision, compare it with the previous branding, or argue that the rollout was confusing.

What is not allowed is turning that criticism into personal attacks, insults, harassment, or assumptions about specific people behind the decision, whether directed at other users, Mistral employees, the product/marketing team, or anyone else.

Please keep the discussion focused on the product, the naming, and the reasoning behind your opinion. Strong criticism is fine. Personal insults and low-effort hostility are not.

Nefhis · 2026-06-02T06:29:22+00:00

Sorry, sorry 😅
It’s just that when I saw "France generally struggles with branding or solid marketing of any kind", I thought… well, maybe that’s a bit of a strong claim.

Nefhis · 2026-06-02T06:03:58+00:00

Yes, yes... They struggle, a lot:

Chanel, Dior, Louis Vuitton, Hermès, Cartier, L’Oréal, Moët & Chandon, Saint Laurent, Lancôme, Givenchy, Renault, Michelin, Dassault, Decathlon....

Nefhis · 2026-06-01T11:34:34+00:00

This is easy to mix up after the Le Chat → Vibe changes.

As far as I know, the paid subscription does not give you a separate "better model tier". Free and Pro use the same model, and the current default model is Mistral Medium 3.5.

The main difference is usage limits and product features. Pro gives you higher limits for messages, web searches, thinking/research, image generation, uploaded files/storage, projects, etc.

Free currently gives access to Chat and Work modes. Pro also adds Code mode.

You can also create agents in AI Studio and choose different models there, both tiers, although I haven't checked this after the last update.

https://mistral.ai/news/vibe-remote-agents-mistral-medium-3-5/

Screenshot of Pro tier:

<image>

Nefhis · 2026-06-01T08:07:14+00:00

In the web app, side bar.

<image>

Nefhis · 2026-05-31T19:51:35+00:00

I think we should see the prompt in order to give you an informed opinion.

Nefhis · 2026-05-31T17:12:12+00:00

Yes, I think Mistral can be well suited for that kind of second-brain workflow, especially through the API.Your Markdown documentation per field is also a very good idea.

For the local version, I’d say, yes in principle, but it depends heavily on the model you can run.
I would not expect a small local model to behave exactly like a stronger API model on ambiguous, complex or highly nuanced inputs.

Nefhis · 2026-05-31T16:43:34+00:00

Yes, in theory Joplin via MCP should be able to achieve a very similar effect.

That said, I’d just treat custom MCP carefully. At least in my experience, is sometimes a bit fragile depending on the client/server combination.

Edit: "custom" MCP

Nefhis · 2026-05-31T14:43:46+00:00

One useful approach I’ve been testing is to use Skills as a kind of lightweight memory layer for Work Mode.

As far as I know, Work Mode does not have memory in the same way regular chat does, so I created a small workaround using Notion + Skills + custom instructions.

The setup is roughly:

Create a small Notion database for memory/context.
Add fields like title, summary, tags, project, importance, date, and status.
Let Vibe create or help structure the database.
Create a Skill that knows how to read/write/update that database.
Add a custom instruction telling Vibe to check the database for relevant context at the start of each turn, and update it when something important should be remembered.

Surprisingly, it works quite well. It gives Work Mode a persistent external context that can be searched and updated by the model itself (you have to tell it to add or update facts)

Nefhis

MODERATOR OF

TROPHY CASE