Add pre_agent hooks to block, rewrite, or inject context before the model reads a message
Vibe 3.1.1 adds pre_agent, notification, session_start, and session_end hooks, /vibe:import, agentWorktrees with enter_worktree, and vim_keybindings. Plugin skills now use the plugin name (my-plugin:review), not the tool namespace. Wire hooks and rename skill selectors.Why this loop
v3.1.1 adds four hook points around the agent loop. pre_agent runs before the model reads a user message and can block it, rewrite its text, or add context. session_start runs when a session starts, resumes, is cleared, or forked and can add context for the next message. notification runs in the background when Vibe needs approval or an answer, or when a turn completes or fails. session_end runs in the background when a session ends, with reason exit, clear, or other. Quitting waits up to 5 seconds for still-running notification and session_end hooks. Use these instead of prompt prefixes for policy and context. The same release adds /vibe:import, which finds setup from other coding agents and imports instructions, skills, subagents, commands, hooks, MCP servers, and permissions. App servers can advertise agentWorktrees: sessions get the enter_worktree tool, the agent asks whether to work in a new git worktree or in place before editing the checkout, and each worktree is listed in artifacts/list and cleaned up when the session is archived. Plugin skills, knowledge, and agents are now named after the plugin as written (my-plugin:review) instead of its tool namespace (my_plugin:review). Custom agents whose enabled_skills or disabled_skills still use my_plugin:* will not match until they switch to my-plugin:*. vibe-acp notifies the client when an administrator changes the organization's Vibe Code configuration.
Proposed actions
- Add a
pre_agenthook that runs before the model reads a user message and can block it, rewrite its text, or add context for the model. - Add a
session_starthook that runs when a session starts, resumes, is cleared, or forked and injects context into the next message, plus a backgroundsession_endhook that receives the reason (exit,clear, orother). - Add a background
notificationhook that fires when Vibe needs your approval or an answer, or when a turn completes or fails; quitting waits up to 5 seconds for it. - In the Vibe prompt, run
/vibe:importto find your setup from other coding agents and import instructions, skills, subagents, commands, hooks, MCP servers, and permissions. - In every custom agent, change
enabled_skillsanddisabled_skillsfrom the tool namespace (my_plugin:*) to the plugin name as written (my-plugin:*); skills are nowmy-plugin:review, notmy_plugin:review.
Agent prompt
Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI costAGENTS.md / CLAUDE.md / GEMINI.md rule update
DevAgentRadar → Repo Harness Rule Patch
Goal: update our repository's permanent harness instructions based on this release.
Update the file that tool actually reads. Do not dump everything into one file.
- Claude Code → CLAUDE.md plus
.claude/(skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with@AGENTS.md. - Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
- Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if
context.fileNameis set. - Cursor glob-scoped rules →
.cursor/rules/*.mdc(plain.mdis ignored), not a second constitution. - Codex MCP →
.codex/config.toml, not.mcp.json. - Copilot extra instructions →
.github/copilot-instructions.md; custom agents →.github/agents/. - Windsurf →
.windsurf/rules(do not assume AGENTS.md). - Cline →
.clinerules. - Procedures → a skill (
SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents. - Do not fork the same rule into three tool files.
Context
Assistant: Mistral Vibe Proposal: Add pre_agent hooks to block, rewrite, or inject context before the model reads a message Summary: Vibe 3.1.1 adds pre_agent, notification, session_start, and session_end hooks, /vibe:import, agentWorktrees with enter_worktree, and vim_keybindings. Plugin skills now use the plugin name (my-plugin:review), not the tool namespace. Wire hooks and rename skill selectors. Primary source: https://github.com/mistralai/mistral-vibe/releases/tag/v3.1.1
Why it matters
v3.1.1 adds four hook points around the agent loop. pre_agent runs before the model reads a user message and can block it, rewrite its text, or add context. session_start runs when a session starts, resumes, is cleared, or forked and can add context for the next message. notification runs in the background when Vibe needs approval or an answer, or when a turn completes or fails. session_end runs in the background when a session ends, with reason exit, clear, or other. Quitting waits up to 5 seconds for still-running notification and session_end hooks. Use these instead of prompt prefixes for policy and context. The same release adds /vibe:import, which finds setup from other coding agents and imports instructions, skills, subagents, commands, hooks, MCP servers, and permissions. App servers can advertise agentWorktrees: sessions get the enter_worktree tool, the agent asks whether to work in a new git worktree or in place before editing the checkout, and each worktree is listed in artifacts/list and cleaned up when the session is archived. Plugin skills, knowledge, and agents are now named after the plugin as written (my-plugin:review) instead of its tool namespace (my_plugin:review). Custom agents whose enabled_skills or disabled_skills still use my_plugin:* will not match until they switch to my-plugin:*. vibe-acp notifies the client when an administrator changes the organization's Vibe Code configuration.
Suggested actions
- Add a
pre_agenthook that runs before the model reads a user message and can block it, rewrite its text, or add context for the model. - Add a
session_starthook that runs when a session starts, resumes, is cleared, or forked and injects context into the next message, plus a backgroundsession_endhook that receives the reason (exit,clear, orother). - Add a background
notificationhook that fires when Vibe needs your approval or an answer, or when a turn completes or fails; quitting waits up to 5 seconds for it. - In the Vibe prompt, run
/vibe:importto find your setup from other coding agents and import instructions, skills, subagents, commands, hooks, MCP servers, and permissions. - In every custom agent, change
enabled_skillsanddisabled_skillsfrom the tool namespace (my_plugin:*) to the plugin name as written (my-plugin:*); skills are nowmy-plugin:review, notmy_plugin:review.
Config surfaces this release may change
- skills (high confidence) — check your repo before applying
- context and compaction settings (high confidence) — check your repo before applying
- hooks — check your repo before applying
- permission rules — check your repo before applying
- MCP servers — check your repo before applying
- subagent definitions — check your repo before applying
- background and headless runs — check your repo before applying
After you finish
Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.
Tell the human: open https://devagentradar.com/proposals/mistral-vibe-v3-1-1-add-pre-agent-hooks-to-block-rewrite-or-inject-conte and mark Applied, Skipped, or Failed. Proposal id: 8876757d-9406-4d2a-8505-de75489de554
Instructions:
- Read the existing context files and settings for the tools in this repo.
- Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
- Call out deprecated flags, obsolete habits, or changed permission boundaries.
- Do not touch application logic.
Start with the proposed diff and say which layer and which tool's file it belongs in.
Your loop
This browser · no sign-in · not shared as “you”After you run the prompt
Only you can mark this. Agents cannot write your loop.
Your decision stays on this device. A public tally appears after a few votes.