Mistral Vibe: Agents Can No Longer Decide What Runs Without Asking

Mistral VibeView original changelog

Mistral Vibe 3.1.4 now ignores an agent's safety, bypass_tool_permissions and permission = "always" settings, so a session runs the user's approval policy whatever its agent. A project's .vibe/agents/ can no longer redefine an approval policy, and sub-sessions cannot gain a looser policy than their parent.

Key Takeaways

  • Agent files can no longer grant themselves auto-approval through safety, bypass_tool_permissions or permission = "always".
  • A repository's .vibe/agents/ cannot redefine approval policies; the file is ignored with a config issue.
  • Sessions started by other sessions and forks inherit the parent's policy, and requests for looser ones are refused.
  • Custom agents that relied on auto-approve must now set default_approval_policy or --approval-policy auto-approve.
  • Tools set to permission = "never" are disabled under auto-approve instead of running.
  • Reopened sessions with an unavailable policy fall back to ask and say so.

Approval is the user's decision

In Mistral Vibe 3.1.4 an agent no longer decides what runs without asking. Its safety, bypass_tool_permissions and permission = "always" settings are ignored, and a session runs the user's default_approval_policy regardless of the agent. To keep a custom agent running in auto-approve, users set default_approval_policy = "auto-approve" or pass --approval-policy auto-approve. An agent can still narrow a tool to ask or never. Other settings an agent may not set, such as a tool allowlist, sensitive_patterns, enabled_agents or enable_auto_approve, are ignored and listed as config issues.

Project files cannot redefine policies

A project's .vibe/agents/ can no longer redefine an approval policy (ask.toml, auto-approve.toml and so on). The file is ignored with a config issue, while overrides in ~/.vibe/agents/ still apply. Under auto-approve, tools that a custom agent sets to permission = "never" are disabled rather than auto-run.

Sub-sessions and resumed sessions

Sessions started by another session, and forks, run the approval policy of the session they come from, and a start that asks for another policy or for auto-approve is refused. A reopened session whose approval policy is no longer available continues in ask rather than the default policy, and says so.