Hook event
A structured message that an AI coding agent emits at a defined point in its lifecycle — after a tool runs, when a turn ends, when a session starts. VibeMon's original client was built on these events.
A hook event is a JSON payload that an AI coding agent (Claude Code, Codex, Cursor, Gemini CLI) produces at a hook point — PostToolUse, Stop, UserPromptSubmit, SessionStart, Notification, or the agent-specific equivalents.
VibeMon's original client was built entirely on hook events: its install script configured each supported agent to POST a small event envelope to a VibeMon endpoint. That client sent event metadata — the event type, timestamp, agent name, the path of the file being edited, repo, branch and commit SHA, a session ID and, by default, the first line of the commit message — and never source code, file contents, prompt text or AI completions.
Today's one-command installer sets up the AttemptDB connector instead and replaces the older hooks only after its first successful sync; what it sends is described in the FAQ. Either way, what feeds the garden is what your agent did — edits, commits and passing tests — turned into garden energy.
Related terms
- Garden energy — What the VibeMon garden runs on: activity from your AI coding agents — edits, commits and passing tests — turned into energy that the slime gardeners spend.
- Vibe coding — A programming workflow where a developer prompts an AI coding agent in natural language and reviews the intent of the output rather than the syntax.