Mistral Vibe: Shell Commands That Read Protected Files Now Ask First

Mistral VibeView original changelog

Mistral Vibe now asks for approval when a shell command reads protected files, even if the command itself is otherwise allowed, in both POSIX shells and PowerShell. Folders whose only project config is .vibe/hooks.toml or .vibe/skills.toml now also ask to be trusted.

Key Takeaways

  • Protected file reads now need approval even for otherwise allowed commands.
  • The rule covers POSIX shells and PowerShell.
  • When reads cannot be analyzed, approval is scoped to that exact command.
  • Folders with only hooks.toml or skills.toml now prompt for trust.
  • vibe -p warns instead of silently skipping untrusted project config.
  • The change keeps the agent inside what the user authorized.

Closing a gap in command approval

Previously, an allowed command could read protected files without a prompt. In 3.1.3, shell commands that read protected files ask for approval even when the reading command is otherwise allowed. This applies to POSIX shells and PowerShell.

Careful when Vibe cannot tell what is read

Some commands hide which files they touch, through variables, brace expansion, recursive or piped reads, a change of directory or an interpreter wrapper. When Vibe cannot tell exactly which files are read, the approval covers only that exact command, so one approval cannot widen into a blanket permission.

Project config that needs trust

A folder whose only project configuration is .vibe/hooks.toml or .vibe/skills.toml now asks to be trusted. Headless vibe -p warns that such config is ignored until --trust is passed, instead of skipping it silently.