VibeGame: Vibe Your Dream Game -- An open-source self-evolving multi-agent framework with an AI-Native game engine that turns your natural language into a fully playable 2D web game and edit it any way you want, built on Claude Code & Codex.
Hook Claude Code
One of 10 in settings.json
Runs when a session starts on startup and resume, executing session-start.py and web_hook.py via python3 with --source-app and --event-type (2 commands). From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when you submit a prompt, before the agent sees it, executing goal-capture.py and web_hook.py via python3 with --source-app and --event-type (2 commands). From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when a session ends, executing web_hook.py via python3 with --source-app and --event-type. From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs before the agent uses a tool for Agent tool calls, executing web_hook.py, enforce-team-setup.py and enforce-team-mode.py via python3 with --source-app and --event-type (3 commands). From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when the agent asks permission for an action, executing web_hook.py via python3 with --source-app and --event-type. From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when the agent finishes a response, executing agent-team-stop.py via python3 with --source-app. From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when a subagent starts, executing web_hook.py via python3 with --source-app and --event-type. From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs when a subagent finishes, executing web_hook.py via python3 with --source-app and --event-type. From tettethu/VibeGame.
Hook Claude Code
One of 10 in settings.json
Runs after a tool call finishes for SendMessage tool calls, executing teammate-message-touch.py via python3. From tettethu/VibeGame.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: