28 lines
1.5 KiB
Markdown
28 lines
1.5 KiB
Markdown
# Subagents
|
|
|
|
The `subagent` tool starts named definitions as independent child conversations.
|
|
The tool supports `start`, `message`, `wait`, `stop`, and `list`.
|
|
Definitions come from world files and project overlays.
|
|
Only `isolate: none` works until P3-k supplies workspaces.
|
|
A worktree request returns a clear error before it creates a child.
|
|
|
|
An anchor task in the parent owns each child.
|
|
The conversation chain therefore includes the child and its parent.
|
|
A parent stop does not stop the child.
|
|
A child stop cancels captured reporter inputs and current work, but permits later reuse.
|
|
|
|
The reporter uses two durable phases: `deliver` and `report`.
|
|
The delivery phase submits an instruction with a stable request ID.
|
|
The report phase steers the parent with the stored answer and its returned model identity.
|
|
A stable request ID deduplicates each answer across replays and restarts.
|
|
The `afterTools` hook acknowledges committed foreground results and withdraws duplicate reports.
|
|
A foreground wait yields when the parent receives steering. The child continues independently.
|
|
|
|
The recovery observer and startup scan deliver answers to one-way parent messages and parent replies.
|
|
They also recover answers after interrupted or failed delivery.
|
|
They do not report ordinary child inputs or messages from other conversations.
|
|
|
|
The service creates main agent conversations for resident definitions.
|
|
The sections list available definitions and child work that remains active.
|
|
The definitions editor, workspaces, `land`, and `discard` remain outside this extension's current scope.
|