Mistral Vibe: Slash Commands Stop Echoing and Report Results as Status Rows
Mistral VibeMistral Vibe 3.0.4 cleans up how slash commands appear in the transcript. Commands are no longer echoed back, pickers stop printing open and close messages, and outcomes show as compact status rows marked with a check, warning or cross. Content commands such as /help and /status now render like an assistant reply under their own heading.
Key Takeaways
- Slash commands no longer echo in the transcript, which removes repeated noise from long sessions.
- Pickers stop printing open and close messages, leaving only the result that matters.
- Command results appear as one-line status rows marked with a check, a warning or a cross.
/helpand/statusrender like an assistant reply under their own heading, matching the rest of the conversation's formatting.- The cleanup lands in Mistral Vibe 3.0.4 together with broader rendering improvements for markdown, code and diffs.
Less Noise From Commands
Mistral Vibe 3.0.4 reduces the clutter that slash commands left in the transcript. Typing a command no longer echoes it as a message, and pickers no longer print a line when they open or close. The transcript now keeps the conversation and meaningful results rather than a trail of command plumbing.
Outcomes as Status Rows
When a command finishes, its outcome or error is shown as a one-line status row with a clear marker: a check mark for success, a warning sign for a caution, and a cross for a failure. This gives a consistent, scannable way to see whether a command worked, instead of free-form text that varies from command to command.
Content Commands Read Like Replies
Commands that produce content, such as /help and /status, now render like an assistant reply under their own heading. Their output uses the same readable formatting as the rest of the conversation, so longer help text and status details are easier to scan.
Related Release Changes
These changes ship in Vibe 3.0.4 alongside a wider refresh of markdown, code block and diff rendering.