Mistral Vibe: Tool Calls Now Fold Into a Compact Timeline by Default
Mistral VibeMistral Vibe redesigned how tool activity appears in its conversation view, folding tool call groups into a single compact summary line by default instead of printing every step inline. A new Ctrl+O shortcut expands or collapses everything at once, and the summary line switches between present tense ("Running commands") while work is in flight and past tense ("Ran commands") once it finishes. Background process tools like process.start and process.stop now render a typed result widget instead of raw JSON, while output from a bare ! shell command is the one thing that stays visible directly in the timeline rather than folding behind a toggle.
Key Takeaways
- Tool call groups fold by default now, replacing a transcript that used to print every call inline with a single collapsible summary line.
- Ctrl+O is the new master toggle, expanding or collapsing every tool group and result body in the conversation in one keystroke.
- The summary line changes tense as work progresses, reading "Running commands" mid-turn and "Ran commands" once the group finishes.
- Background process tools got a typed widget, showing the command or process ID in the header instead of raw JSON output.
- File edits and writes are folded into the same summary mechanism as other tool calls, keeping the conversation view consistent across call types.
- A developer's own
!shell commands are the one exception, staying visible directly in the timeline instead of collapsing behind the fold.
A Quieter Default View
Mistral Vibe's conversation view has historically printed every tool call the agent makes as its own block, which meant a turn involving a dozen file reads, edits, and shell commands could push a lot of scrollback in front of the actual conversation. With v2.25.1, Mistral Vibe changed that default: tool call groups now fold into a single compact summary line, and a developer clicks to expand the full list only when they want the detail. Pressing Ctrl+O toggles every group and result body in the conversation at once, which is useful for quickly auditing everything an agent did during a long turn.
The summary line itself is dynamic. While a group of calls is still running, it shows a present-tense label like "Running commands"; once the calls finish, the label switches to past tense, such as "Ran commands." File edits and writes are folded in alongside other tool calls rather than being treated as a special case, so the whole surface behaves consistently.
Typed Results for Background Processes
Alongside the folding change, Mistral Vibe gave its background process tools, process.start, process.stop, process.output, process.list, and process.write, a proper typed result widget instead of dumping raw JSON into the transcript. The call header now shows the command or process ID directly, so a developer scanning a long session can immediately see which background process a given call refers to without expanding it.
The One Exception: Raw Shell Output
Not everything got folded. When a developer runs a bare ! shell command themselves, Mistral Vibe now shows its output directly in the timeline, unfolded and ungathered into the summary line that groups the agent's own tool calls. Shell calls the model makes on its own behalf still fold like every other tool result. The distinction keeps commands a developer explicitly typed visible by default, while letting the agent's own bookkeeping stay out of the way.