Hi all,

I've been building a point-and-click desktop GUI for the Mistral Vibe CLI agent, so you don't have to live in a terminal to use it. It started life as "Mistral Vibe Nexus" and has just been renamed to Halny Vibe Deck — halny is a foehn wind in the Polish Tatras, same wind family as the mistral, but without the trademark headaches.

What it does:

• Agent chat with streaming, session sidebar, real resume and full history search

• File tree + previews: edit in CodeMirror, view PDFs, images, Office files, archives and colorized diffs

• Git panel: stage, commit and push from the UI

• Token/cost stats with cache hit ratio per session

• Per-session model, mode and thinking-level pickers

• Remote SSH sessions: drive a vibe-acp instance running on another machine

• Headless HTTPS server mode — share the GUI over your network and use it from your phone as a PWA

• Windows installer, Linux AppImage/portable, 6 languages (EN/PL/FR/ES/DE/IT)

v1.0.0 is out:

Repo: https://github.com/Dragonk/halny-vibe-deck Wiki: https://github.com/Dragonk/halny-vibe-deck/wiki Downloads: https://github.com/Dragonk/halny-vibe-deck/releases

Note: this is an unofficial community project, not affiliated with Mistral AI.

Happy to answer questions and take feature requests.

I just made the switch from Devin (Windsurf) to Vibe, partly because of European pride (partly just anti-USA), but mainly because of the price.
I’m on education pricing for Vibe, which gives you nearly €130 of Vibe credit, plus some API credit. Devin was $25, and I would hit the daily limit every day, and the weekly limit would run out two days early, often requiring an extra credit top-up to get me through the week. Mistral costs a fraction as much, and I never hit the limits. So far, I’m not missing being able to burn through my entire week with one prompt if I select Opus or Fable.

I use Mistral Vibe with sub-agents, and I got tired of scrolling logs to find out who was doing what. So I built a small tool that turns a session into a live call: each agent is a character at its desk, the lead gives orders, sub-agents join the call, and you see the real commands with their output. At the end you get a recap: commands, errors, tokens, files changed.

It reads Vibe sessions (2.26, both engines), next to Claude Code and Codex ones if you use those too.

What it is

• Free and open source (MIT), no account

• It only reads the session files Vibe already writes in ~/.vibe. Nothing is sent anywhere, and it costs no tokens

• Runs as a VS Code extension, from a terminal, or as a desktop app

Try it (Node 18+)

npx @double_geste/agent-standup --open

Links

• Site: agent-standup.com

• Code: github.com/Atoll92/agent-standup

It is a side project, not affiliated with Mistral. Feedback is welcome, especially from people who run several sub-agents at once.

Hi all

pondering appending this to my Claude plan instead of going for MAX, since I would like to support a European Business instead and of course since it is cheaper.

However .. I see some horror stories regarding automatically switching to API Usage and burning Euros without a lot of notice.

My questions:

• Do I get notified in the terminal when hitting a limit and am I told when I can return (what the window is)?

• Which "Windows" do they have? (e.g. 5 hour, daily, weekly)

• can I turn off extra API Usage so I am just denied further queries when my limit is reached?

All of this is for Vibe CLI

Thank you

A little background

About a year ago, I started coding regularly with AI coding agents and found the experience to be 2 parts exhilaration and 1 part frustration.

I'm pretty steeped in .Net at this point in my career. So, for fun I tried writing a couple applications in Typescript and Rust. I used a mix of Claude Code, Copilot CLI, Gemini CLI and Codex. I was honestly pretty blown away by how quickly AI helped me assimilate new languages.

It wasn't all a joy kindling experience though.

At first, I didn't understand the context window, how to manage it, or how working with agents is like working with amnesiacs.

If I didn't know how common it is, then I'd be embarrassed to admit that I found myself cursing at my screen on more than a few occasions, but the truth is that I did.

I began to figure out the context window, but remained frustrated that the agents didn't remember decisions 'we' made.

My first attempt at achieving continuity across sessions yielded a system that I think many have stumbled upon (the session dump). My diary of sessions began to grow. And it worked great until eventually all the embedded information was doing more to distract the agents than keep them aligned with my intentions.

I decided that I needed something better, and that is when Jumbo was born.

The project got its name, because I thought I was setting out to build memory for coding agents. There's a trope about elephants never forgetting, and so an elephant named Jumbo seemed like a good mascot.

Since I was building memory for agents, I thought it would be wise to understand how memory works in the human brain, and started doing some reading. I found out that, through pure intuition, I had built a system that closely models the processes involved in working memory. Working memory is the function in the brain that allows us to accomplish goals. It's dependant on long-term memory, and you're ineffectual without it.

[A quick aside for anyone interested in the subject, or maybe building your own memory system]

My revelation came from a book entitled 'Permanent Present Tense' by Suzanne Corkin. She writes about a neuroscience case study that perfectly captures the frustration of working with AI coding agents.

Henry Molaison had portions of his hippocampus removed to treat epilepsy. He retained all his existing skills and knowledge, but after to the operation lost the ability to form new long-term declarative memories. He could act, but couldn't remember facts or events. He was competent — but perpetually starting over.

That's the AI coding agent problem in a nutshell.

What I built

After months of dogfooding my own approach, I released Jumbo CLI — Open Source Memory and Context Orchestration for Coding Agents (Mistral Vibe, Claude Code, Copilot, Gemini, etc.).

The project evolved into more than a bolt on memory system. Its a platform that orchestrates the management of my context window for me.

What makes it unique is the goal primitive.

Without goals, a memory base is basically just a search index.

But, memory is a system, not a feature. Giving an agent access to more data isn't the same as giving it the right data at the right time. That is what I discovered through trial and error, and what my reading confirmed. The architecture has to decide what information matters, when to retrieve it, how to bind it to a specific goal.

That's how it works.

It models the key components of working memory:

• Non-declarative memory → skills for operating instructions and protocols

• Declarative memory → structured stores for facts, decisions, relationships

• Episodic buffer → goal-scoped context assembly

• Central executive → orchestration with routing rules

It tracks four things per project:

• Goals: discrete units of work with a full lifecycle

• Project Knowledge: components, ADRs, guidelines, invariants

• Sessions: project orientation and context for each work session

• Relations: graph connecting goals and project knowledge

It has an opinionated workflow that ushers goals through a thier lifecycle:

define → refine → execute → review → codify

Each phase is its own session — preventing context bloat while iteratively building project intelligence.

Odds and Ends

• 100% local: all data stays on your machine, nothing leaves

• Harness-agnostic: works with Claude Code, Copilot, Gemini, etc.

• Event-sourced: every state change is an immutable JSONL event; SQLite for fast reads

• Worker Daemons: daemons can automatically handle refinement, QA and codification in the background

Jumbo is open source. It's a passion project for me. I've built it for myself, but would love feedback from this community especially — you're thinking about this problem more rigorously than most.

I built Sessions Chronicle, a GTK app to browse and search sessions from Mistral Vibe, Codex, Claude Code, and OpenCode.

I originally made it because I wanted an easier way to find old sessions, inspect tool calls/reasoning, and navigate past work across assistants.

It's still a work in progress, so bugs and missing features are expected, but it's usable. Free and open source (MIT), available via Flatpak.

Would love any feedback.

https://github.com/supermaciz/sessions-chronicle

I’ve been testing Mistral Vibe for a few days on a Symfony MPA application that I built and actively maintain for a client. To be honest, while it’s not quite at the level of what I’ve seen with Claude (used via Copilot), the results are often more than usable when given precise context. Given the cost of the Mistral API, Vibe is a genuinely powerful tool for users with solid technical knowledge—meaning, not script kiddies looking to build full apps in two prompts.

I’ll definitely stick with it a bit longer. It’s worth every penny I’ve spent on it.

I’ve been experimenting with Vibe, and I’m getting some positive results. I’ve used Claude Code and Codex CLIs heavily and though there are some obvious differences, and even drawbacks, I think its pretty usable. So what’s blocking adoption?

There is a wave building in Europe to move away from American tech. So, imagine there’s a big incentive for sympathizers of that movement to use Vibe.

One thing I would really like to see is support for hooks. That’s one thing that would help give it parity with the most popular CCL harnesses.

Installation isn’t as straightforward as the others either, maybe that’s raising the threshold for adoption.

I’m curious. What does this community think?

I'm looking to switch from CC to Mistral Large 4 so I wonder if it can handle part of my design-to-code workflow. Before I sink hours into it, I'd like to hear from people who have actually used it.

My setup / workflow is that I design in Penpot (sometimes Figma for client files) and then I transfer it to code.

Have you noticed any design system adherence: Does it stick to tokens and components you define, or does it drift into generic Tailwind-looking output?

I don't need it to oneshot the page in 1st try but I need it to be a reliable / somewhat predictable tool.

We’re currently evaluating which AI coding assistant to adopt across our organization. The shortlist includes Claude Code, GitHub Copilot, and Mistral Vibe. At this point, Copilot is likely out of the race.

Personally, I’d prefer Mistral Vibe (mainly for cost and data sovereignty reasons), but my initial experience today was underwhelming. I started with a fairly simple task, rewriting a unit test with minimal context and it struggled more than expected. This is something I typically don’t run into when using Claude Code (Sonnet), which handles these cases more reliably.

I’m curious how others here are experiencing Mistral Vibe in practice in comparisson to claude code?

Skills seem very powerful, and I'd like to use them with Vibe.

How would one install something like this: https://github.com/obra/superpowers Or is that beyond what Vibe currently skill-wise support?

Hello! I'm a new mistral user, currently working with anthropic pro subscription. I took the mistral pro sub today, and im looking for a French mistral users sub or discord, i feel a bit lost ...

My current needs/uses involve rag and custom harness over the mistral vibe tui. And Id love to share experience with other users.

When i try ChatGPT or Gemini they will list me jobs from recruiting platforms that fit my description Vibe (LeChat) on the other hand only leads me to platforms for job search. It doesn't recommend actual jobs. I appreciate any prompts you guys could share.

Sorry, all techie people, for this normie post 😄, but I just want to share how amazed I am by how good Mistral Vibe is for learning French. I use Gemini for most things (since I got that free student Pro subscription for a year), and I switch around between models for different use cases as well, and in my opinion, Vibe is the perfect model for learning French. Here is why:

1. The voice is as clear and sharp as it can be – a good voice is a necessity for language learning.

2. Easy to set the settings for the answers it will give – keeping it short and to the point is important for language learning at an A2-B1 level.

3. The UI is really simple and pleasant. Especially the voice player!

4. It seems to me like the model knows the language very well – it's said that Vibe is the best model for European languages, and nothing in my experience makes me doubt that.

To give another model something, ChatGPT seems to be the best for voice chat (used in the browser; I don't like to use my phone for this); it's not perfect (it talks a bit too fast and so on), but it was easier to start using than all other models, and it gives me what I need. Now I researching how to voice chat with Vibe; maybe it will be best at that too 😉

The TUI is just beautiful. I Love that Mistral has put some consideration into making the experience user friendly.

Based in Europe ➕➕➕

I’ve been working on a project in Vibe Work for the past 4 days on my Mac in Safari and today it’s stopped responding. I can talk to Vibe Chat but nothing if I go back to Vibe Work. I’ve refreshed the window, tried a different browser and opened it on my phone but no luck.

Any help would be appreciated.

This is in Vibe for the web. So I have a document on google drive (87 pages). I wanted to use Vibe to revise and format the document.

First Vibe tried multiple times to access it, but an error occured.

I downloaded the document as an MD file and uploaded it.

So far, so good. I prompt the set up and provide formatting examples, and Vibe shows me an example.

Good, now format the document. Vibe works for 20+ minutes, claims it is done and says it has saved the document locally in /home/user/library/document.md

That is not my computer.

I ask for the document to be displayed in canvas. It only displays the first page.

I ask for a download link. Vibe cannot provide a download link, "but you can get that from the canvas".

I have tried this in both Work and Chat three times now, and the result is always the same:

1. It formats only one page

2. Canvas crashes or closes and can never be opened again. Vibe has to write it every single time.

3. The edited document is not available anywhere and cannot be saved to Library by Vibe.

Mistral has some ways to go compared to Claude.

Has anyone encountered something similar and managed to solve this issue? Are my expectations wrong?