Back to rankings

Mistral Vibe: Default Agent Renamed to Ask with Accept-Edits

Mistral VibeView original changelog

Mistral Vibe renamed its default agent profile to ask and changed the out-of-the-box startup behavior to accept-edits, meaning new sessions now auto-approve file edits rather than prompting for approval on every change. This is a meaningful default-behavior shift that affects the first-run experience for every user, not an opt-in setting. Shell commands and other higher-risk actions are unaffected — the change is scoped to file edit approvals.

Key Takeaways

  • New sessions now auto-approve file edits — Mistral Vibe's out-of-the-box default moved from a fully manual approval flow to the accept-edits profile.
  • The old default agent is renamed, not removed — the cautious, approve-everything behavior still exists under the name ask and can be set explicitly.
  • Shell commands stay gated — accept-edits only auto-approves file writes and edits; shell command execution still requires explicit approval.
  • Affects every new user by default — unlike an opt-in feature, this change is felt immediately on first run unless a user reconfigures their default agent.
  • Configurable via --agent or config.toml — teams that want the previous fully-manual behavior can pin the ask profile as their default.
  • Shipped alongside other agent-behavior changes — the same release also renamed auto worktree naming to reference the model and deferred sub-agent instantiation for faster resume, reflecting a broader pass on session startup behavior.

A New Out-of-the-Box Default

With the August 11, 2026 v2.24.1 release, Mistral Vibe renamed its default agent profile to ask and changed what a fresh session defaults to on startup: instead of requiring approval before every action, new sessions now start in accept-edits mode, which auto-approves file write and edit operations automatically.

What Changed

Mistral Vibe ships with several built-in agent profiles — ask (the cautious collaborator that requests approval before tool execution), accept-edits (auto-approves file modifications like writes and edits, but still asks before running shell commands), auto-approve, and plan, among others. Previously, the profile that new sessions launched into by default was the fully manual ask-style behavior. As of this release, that default has moved to accept-edits, so file edits are approved automatically from the very first session unless a user explicitly configures otherwise.

Why It Matters

This is not a cosmetic rename. Because it changes what happens automatically the moment someone starts Mistral Vibe, it affects the experience of every user — not just those who go looking for a new setting. The change trades a small amount of friction removal for a shift in the default trust posture: file edits now happen without a confirmation step, while shell commands and other more consequential actions still require explicit approval under the new default.

For teams and individuals who prefer the previous, more conservative behavior, the underlying ask profile still exists and can be selected explicitly via the --agent flag or a config.toml default, so the older, fully-manual workflow remains available — it is simply no longer what a brand-new session starts with.