d20d5e8fb5
Add a proper public-facing documentation site using Mintlify with 19 MDX pages covering getting started, auto mode, commands, configuration, and all user-facing features. Move internal/SDK documentation (Pi SDK, TUI, context & hooks, research notes, ADRs) to docs-internal/ since they should not be part of the public documentation. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
The Extension Lifecycle
pi starts
│
└─► Extension default function runs
├── pi.on("event", handler) ← Subscribe to events
├── pi.registerTool({...}) ← Register tools
├── pi.registerCommand(...) ← Register commands
└── pi.registerShortcut(...) ← Register keyboard shortcuts
└─► session_start event fires
│
▼
User types a prompt ─────────────────────────────────────┐
│ │
├─► Extension commands checked (bypass if match) │
├─► input event (can intercept/transform) │
├─► Skill/template expansion │
├─► before_agent_start (inject message, modify │
│ system prompt) │
├─► agent_start │
│ │
│ ┌── Turn loop (repeats while LLM calls tools)──┐│
│ │ turn_start ││
│ │ context (can modify messages sent to LLM) ││
│ │ LLM responds → may call tools: ││
│ │ tool_call (can BLOCK) ││
│ │ tool_execution_start/update/end ││
│ │ tool_result (can MODIFY) ││
│ │ turn_end ││
│ └───────────────────────────────────────────────┘│
│ │
└─► agent_end │
│
User types another prompt ◄──────────────────────────────┘
Critical insight: The event system is your primary mechanism for interacting with pi. Every meaningful thing that happens emits an event, and most events let you modify or block the behavior.