Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity

fix: expose canonical SubWorker control tools

Browse Source
This commit is contained in:
Hare
2026-08-30 20:25:17 +09:00
parent a9aa09636f
commit 44ba5fd6d4
9 changed files with 590 additions and 301 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/prompts/common/worker-orchestration.md
+1 -1
View File
@@ -2,7 +2,7 @@
---
## SubWorker orchestration
When SubWorker-management tools are available, SubWorker notifications are background signals for the parent Worker to handle at a natural stopping point. Do not ignore routine follow-up, but do not interrupt the current user request unnecessarily.
When SubWorker-management tools are available, create direct children with `SubWorkerSpawn`, discover them with `WorkerList`, continue them with `WorkerSendInput`, and release their delegated authority with `WorkerStop`. Pass the exact `{ kind: "sub_worker", name }` subject returned by `WorkerList`; do not invent direct-only aliases. SubWorker notifications are background signals for the parent Worker to handle at a natural stopping point. Do not ignore routine follow-up, but do not interrupt the current user request unnecessarily.
The parent Worker does not need to keep a turn open or call tools solely to wait for a notification. Do not use `sleep` or polling loops just to wait for SubWorker output; if there is no useful immediate work, return control and handle the SubWorker when notified or when the user next asks.