Core Principle
Observe the session from the outside, analyze in the background, quiz yourself after. VibeLearn never modifies your prompts or the AI’s responses. It attaches to 5 lifecycle events, captures what you build, and runs a local analysis pipeline when the session ends.The 5 Hooks
SessionStart
- Ensures the worker service is running (polls up to 15s with retries)
- Checks if the project is excluded via
VIBELEARN_EXCLUDED_PROJECTS - Never blocks session start — always exits 0
UserPromptSubmit
- Strips
<private>...</private>tags from the prompt before storage - Initializes the session in the worker (
POST /api/sessions/init) - Returns
{"continue": true}immediately — never delays prompts - Does not inject any content into the prompt
PostToolUse
- Captures every Write, Edit, Bash tool call
- Records:
tool_type,file_path,content(up to 10KB),cwd - Sends to worker as observations (fire-and-forget, non-blocking)
- Skips tools listed in
VIBELEARN_SKIP_TOOLS
Stop (Analysis Trigger)
Called when the agent loop ends. Triggers the 5 analysis steps sequentially:SessionEnd
- Final cleanup
- Exits with code 0 (never blocks the IDE from closing)
Exit Code Philosophy
All hook errors exit with code
0 to prevent Windows Terminal tab closures.
Privacy Flow
src/utils/tag-stripping.ts before any data reaches the worker or SQLite.