Mistral Vibe: Full Prompt Queue Management
Mistral VibeMistral Vibe overhauled its prompt queue, adding select, edit, remove, pause, and resume controls that now run through the app server. Developers can fix or drop a queued prompt without waiting for the current turn to finish. The CLI now sends a batch of queued prompts as a single turn, while Desktop still sends them turn-by-turn, a small but noticeable divergence between surfaces.
Key Takeaways
- Queued prompts gain full lifecycle controls: select, edit, remove, pause, and resume, run through the app server instead of a fire-and-forget queue.
- CLI and Desktop now diverge on delivery: the CLI batches queued prompts into a single turn, while Desktop still sends them turn-by-turn.
- The overhaul builds directly on the original message-queue feature from v2.15.0, turning a basic "type while the agent works" queue into a managed workspace.
- Editing a queued prompt before it's sent removes a common frustration: no more waiting for a turn to finish just to fix a typo.
- The app-server-backed design suggests Mistral Vibe is centralizing more session logic outside the terminal renderer, likely easing future cross-surface consistency.
- Power users who stack multiple instructions while an agent works will notice the most immediate day-to-day impact of this release.
From Simple Queue to Managed Workspace
Mistral Vibe overhauled its prompt queue, the feature that lets developers keep typing instructions while the agent is still working through a previous turn. What started in v2.15.0 as a basic "type while the agent runs" queue now runs through the app server and exposes full lifecycle controls: developers can select, edit, remove, pause, and resume queued prompts before they are sent.
Editing Before Sending
The ability to edit a queued prompt is likely the most immediately useful addition. Previously, a typo or a change of mind meant waiting for the current turn to finish before correcting course. Now developers can fix a queued instruction in place, or remove it entirely, without interrupting the agent's current work.
CLI and Desktop Diverge on Delivery
The update also introduces a difference in how queued prompts reach the agent depending on the surface. The Vibe CLI now sends a batch of queued prompts as a single combined turn, while the Desktop app continues to send them turn-by-turn. Developers moving between the two surfaces should expect slightly different behavior when multiple prompts are queued up.
Routing prompt queueing through the app server also suggests Mistral Vibe is consolidating more session logic outside the terminal renderer itself, a change that should make it easier to keep behavior consistent as more clients, including the CLI, Desktop, and IDE extensions, come online.