Mistral Vibe: Programmatic Runs Report Denied Tool Calls and Empty Answers

Mistral VibeNov 9, 2026View original changelog

vibe -p now reports each denied tool call on stderr and in the export's warnings, and says on stderr when the agent finishes without an answer. Commands the agent runs also get VIBE_SESSION=1 so scripts can detect they run under Vibe.

Key Takeaways

vibe -p now logs every denied tool call to stderr and the export's warnings.
It also warns on stderr when the agent finishes without an answer.
These changes make CI and scripted runs easier to debug.
Agent-run commands get VIBE_SESSION=1 in their environment.
Scripts can use the variable to detect they run under Vibe.
It shipped in Mistral Vibe 3.1.1.

Fewer silent failures in scripts

In programmatic mode, Mistral Vibe 3.1.1 prints each denied tool call on stderr and records it in the export's warnings. It also says on stderr when the agent finishes without producing an answer, so a run that quietly did nothing is easier to catch.

Detecting Vibe from a script

Commands the agent runs now have VIBE_SESSION=1 in their environment. Scripts and shell profiles can use it to behave differently when running under Vibe.