Hook-Activation Restart Documentation
Agents Remember 0.9.4
Docs release. A newly-installed session-start hook only takes effect on the next session (harnesses load/snapshot hooks at startup), so it needs its own restart — a third one beyond "load the server" and "discover the skills". This was undocumented, so a developer could place the hook and assume it was already active.
Highlights
README.md+mcp/README.md: Quickstart now states three restarts (load server / discover skills / activate hook).docs/install/claude-code.md: explains thesettings.jsonsnapshot-at-startup behavior and the post-install restart.docs/install/codex.md,pi.md,openclaw.md,antigravity.md: note that C-13 can install a start hook (more authoritative than the AGENTS.md import) and that a newly-installed hook needs a restart to activate; OpenClaw's note distinguishes it from the timeout-settings restart.C-13-install-and-onboardSKILL.md: Stage 1 and Report Result now tell the developer to restart so the hook activates (harness-agnostic).
Instruction-file harnesses (Cursor, VS Code + Copilot, Hermes) are intentionally left unchanged: their always-read files need no restart.