fix(hooks): run plugin triggers with HTTP hooks disabled (#131059)

* fix(hooks): schedule plugin turns independently of HTTP hooks

* docs(hooks): clarify shared HTTP capacity reservation
This commit is contained in:
Peter Steinberger
2026-08-27 11:34:07 -07:00
committed by GitHub
parent 2f13a37a82
commit b3eded1744
3 changed files with 136 additions and 83 deletions
+4 -2
View File
@@ -416,8 +416,10 @@ snapshots; OpenClaw owns all persistence and lifecycle coordination.
<Accordion title="api.runtime.hooks">
Dispatch isolated agent turns for untrusted external-content triggers, such
as an email watcher. Unlike `api.runtime.subagent.run(...)`, hook dispatch
wraps external content, serializes runs for the same session, and uses the
Gateway hook execution lane and completion reporting.
wraps external content, serializes runs for the same session, and reports
completion through the Gateway. Plugin turns share the cron execution
budget without requiring the HTTP hooks endpoint. When HTTP hooks are
enabled, one slot in that shared budget remains reserved for HTTP work.
```typescript
const result = await api.runtime.hooks.dispatchHookAgentTurn({