Let agents supervise and follow up with subagents
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- ai-infra-agents, backend
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenPetsHQ/openpets#273 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fritzprix/libr-agent#2161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
blackboardsh/electrobun#581 ·
-
backlog-skill effort:xs frontend infra ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
LucasSantana-Dev/Lucky#2862 ·
Maintainers usually reply within 1 day