From 997d80bc69a6363e8c65a987dace0e30d761522d Mon Sep 17 00:00:00 2001 From: t Date: Mon, 31 Aug 2026 10:17:11 -0600 Subject: 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. --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index e985c18..6841ed9 100644 --- a/README.md +++ b/README.md @@ -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 -- cgit v1.3