docs: fix stale Future Events and wrong log example in hooks.md

- Future Events: session:start/session:end are live plugin hooks, clarify they are planned for internal event stream only
- Log example: session-memory listens to command:new AND command:reset, not just command:new
This commit is contained in:
Vincent Koc 2026-03-30 09:43:01 +09:00
parent 82b6bd7457
commit b7e2e1b399
1 changed files with 6 additions and 4 deletions

View File

@ -576,10 +576,12 @@ Compaction lifecycle hooks exposed through the plugin hook runner:
### Future Events
Planned event types:
The following event types are planned for the internal hook event stream.
Note that `session_start` and `session_end` already exist as [Plugin Hook API](/plugins/architecture#provider-runtime-hooks) hooks
but are not yet available as internal hook event keys in `HOOK.md` metadata:
- **`session:start`**: When a new session begins
- **`session:end`**: When a session ends
- **`session:start`**: When a new session begins (planned for internal hook stream; available as plugin hook `session_start`)
- **`session:end`**: When a session ends (planned for internal hook stream; available as plugin hook `session_end`)
- **`agent:error`**: When an agent encounters an error
## Creating Custom Hooks
@ -996,7 +998,7 @@ metadata: { "openclaw": { "events": ["command"] } } # General - more overhead
The gateway logs hook loading at startup:
```
Registered hook: session-memory -> command:new
Registered hook: session-memory -> command:new, command:reset
Registered hook: bootstrap-extra-files -> agent:bootstrap
Registered hook: command-logger -> command
Registered hook: boot-md -> gateway:startup