Replies: 3 comments 1 reply
-
|
+1, forcing the use of specific commands instead of others seem like a common use case for hooks. |
Beta Was this translation helpful? Give feedback.
-
|
More generally, any time the model tries to do something stupid (whether it be running a certain command or trying to add a certain piece of code), it would be great if we could catch it with a hook and tell it to do something else. In an ideal world, putting sufficient instructions into |
Beta Was this translation helpful? Give feedback.
-
|
+1 to me it also can help with security to make sure the agent is not performing certain tasks like git push for instance. |
Beta Was this translation helpful? Give feedback.
-
|
Hooks support would be useful for tools that manage multiple agent sessions. I maintain a tmux-based workspace manager for AI coding agents. It uses hooks to track agent status and display it in the tmux window list, so you can see which agents are working, waiting for input, or done. 
Without hooks, there's no reliable way to know what state the agent is in from the outside. A minimal set of lifecycle hooks would be enough for this use case:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Component
CLI
Problem statement
I would want to run pre-defined shell commands based on events in Vibe, like Claude Code Hooks.
Use cases would be for example trigger run of a linter or adding extra guardrail pre/post tool call.
Proposed solution
Allow users to specify in the configuration a shell command to run after or before certain events in Vibe CLI.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions