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

ticket: supplement pod orchestration guidance

Browse Source
This commit is contained in:
Keisuke Hirata 2026-06-01 09:57:09 +09:00
parent 3ea005822e
commit 2d4ffe0bce
No known key found for this signature in database
2 changed files with 17 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
work-items/open/20260527-194421-pod-orchestration-system-guidance/item.md
View File

@ -7,7 +7,7 @@ kind: feature
priority: P2 priority: P2
labels: [pod, workflow, prompt] labels: [pod, workflow, prompt]
created_at: 2026-05-27T19:44:21Z created_at: 2026-05-27T19:44:21Z
updated_at: 2026-05-27T19:44:43Z updated_at: 2026-06-01T00:57:03Z
assignee: null assignee: null
legacy_ticket: null legacy_ticket: null
--- ---

16
work-items/open/20260527-194421-pod-orchestration-system-guidance/thread.md
View File

@ -55,4 +55,20 @@ AGENTS.md や workflow に multi-agent の運用は書かれているが、こ
- TUI notification UI の変更。 - TUI notification UI の変更。
---
<!-- event: comment author: hare at: 2026-06-01T00:57:03Z -->
## Comment
## Supplemental guidance from dogfooding
Add two explicit rules to the Pod orchestration/system guidance:
- A spawned Pod completion notification is delivered as a normal background signal. The parent does not need to keep the turn open or call tools solely to wait for it; it is acceptable to finish the current turn and handle the notification at the next natural point.
- Do not use `sleep`/polling loops just to wait for a Pod's output. If there is no other useful immediate work, return control to the user instead of blocking the turn; when the notification arrives, read the Pod output then.
Rationale: during multi-agent work, waiting with `sleep` wastes the active turn and fights the notification model. The desired behavior is notification-driven follow-up, not artificial polling.
--- ---