diff options
| author | t <t@tjp.lol> | 2026-08-31 10:17:11 -0600 |
|---|---|---|
| committer | t <t@tjp.lol> | 2026-09-02 08:26:58 -0600 |
| commit | 997d80bc69a6363e8c65a987dace0e30d761522d (patch) | |
| tree | 9b5a991a920cbee0d6e8c4e841ec7d28912d2f3a /README.md | |
| parent | 7a31ae2163f4ce1c6807da1737203d1063839c14 (diff) | |
Expose background workflow activity events
Bracket each background workflow with lifecycle events and emit its primary
wake before completion so integrations do not report a premature idle state.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 6 |
1 files changed, 4 insertions, 2 deletions
@@ -142,8 +142,10 @@ starts model-authored workflows in a restricted environment and returns a session-scoped workflow ID immediately. Work continues on Pantograph's event loop; completion wakes the primary, and later calls can inspect field-read-only records through `subagents.workflows[id]`, including named child status and -outputs. Every `ctx:agent` needs a workflow-unique `name`, and the callback must -return the workflow's string result. +outputs. While one is live the extension emits balanced `background_work_start` +and `background_work_end` events, allowing lifecycle integrations to remain +busy across the primary turn boundary. Every `ctx:agent` needs a workflow-unique +`name`, and the callback must return the workflow's string result. The same read-only workflow records are exposed to other extensions as `panto.ext.workflows`. Extensions can iterate this table or look up an ID; each |
