Back to rankings

Mistral Vibe: Four New Hook Events for Prompts, Notifications and Sessions

Mistral VibeView original changelog

Mistral Vibe added four hook events: pre_agent, notification, session_start and session_end. They let users block or rewrite a message before the model reads it, get alerted when Vibe needs input, and react to session lifecycle events. Quitting now waits up to 5 seconds for running notification and session_end hooks.

Key Takeaways

  • pre_agent hooks can block, rewrite or add context to a message before the model reads it.
  • notification hooks fire when Vibe needs approval, an answer, or when a turn completes or fails.
  • session_start hooks cover start, resume, clear and fork, and can inject context.
  • session_end hooks run in the background with an exit, clear or other reason.
  • Quitting waits up to 5 seconds for running notification and session_end hooks.
  • Together they extend hooks from tool calls to the whole prompt and session lifecycle.

Hooks before the model acts

pre_agent hooks run before the model reads a user message. They can block the message, rewrite its text, or add context for the model.

Hooks that tell you when Vibe needs you

notification hooks run in the background when Vibe needs approval or an answer, or when a turn completes or fails. This makes desktop alerts or chat pings straightforward.

Session lifecycle hooks

session_start hooks run when a session starts, resumes, is cleared or forked, and can add context for the model to the next message. session_end hooks run in the background when a session ends, with the reason (exit, clear or other).

Quitting behavior

Quitting Vibe now waits up to 5 seconds for notification and session_end hooks that are still running, so cleanup or notifications are not cut off.