Let agents supervise and follow up with subagents
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 48/100
- Issue 類型
- 功能
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Start with the native subagent tool implementation and the child-chats/task primitives from pi that the issue says to reuse, plus issue #19 for how child chats surface in the UI. Map where the tool currently blocks on a final answer and where list/status, follow-up, and interruption would hook in, including lane assignment (shared read-only vs. single-writer) and stop/kill propagation across reconnect. Done looks like a real parallel-review replay in Ace: redirect one child, stop another, inspect partial findings, and integrate results without leaving the app.
由索引模型根據 Issue 內容生成。
描述
The native subagent tool creates durable child chats and can run in a parallel tool batch, but waits for a final answer. The reviewed work also needed partial findings, follow-up instructions, selective interruption, and continued parent work. Opening child chats in the UI (#19) does not supply those operations to the parent agent.
Acceptance
- Start child work while the parent continues; list/status children and inspect partial findings.
- Send corrections and follow-up tasks to an existing child; wait for and collect its eventual result.
- Stop selected work and preserve parent stop/kill propagation and durable ownership across reconnect/restart.
- Read-only reviews may share a lane; writing chats use separate lanes with one writer per lane.
- Replay a real parallel review: redirect one child, stop another, inspect the remaining child, and integrate findings entirely in Ace.
Use pi's existing child chats/tasks rather than another agent state store. Preserve the current one-shot tool where useful. Recursive child creation is separate unless the selected workflow needs it.
Dogfooding core/QOL: #5. Related: #19, #24. Review evidence.
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 0
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
githubnext/ace2 的其他 Issue
-
難度 1/5 1 小時以內 新手友好度 94/100
githubnext/ace2#487 ·
-
難度 2/5 1-3 小時 新手友好度 90/100
githubnext/ace2#486 ·
-
難度 2/5 1-3 小時 新手友好度 67/100
githubnext/ace2#459 ·
-
難度 1/5 1 小時以內 新手友好度 88/100
githubnext/ace2#437 ·
-
難度 4/5 3-5 天 新手友好度 35/100
githubnext/ace2#442 ·
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 74/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 65/100
OpenPetsHQ/openpets#273 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
fritzprix/libr-agent#2161 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
blackboardsh/electrobun#581 ·
-
backlog-skill effort:xs frontend infra ready-for-agent
難度 2/5 1-3 小時 新手友好度 74/100
LucasSantana-Dev/Lucky#2862 ·
維護者通常 1 天內回覆