Add subagent result delivery artifacts
This commit is contained in:
@@ -0,0 +1,37 @@
|
||||
---
|
||||
status: claimed
|
||||
claimed-by: "019fc07d-ab48-7dba-ae9e-caf6bab66d28"
|
||||
claimed-at: "2026-08-01T23:21:43-04:00"
|
||||
parent: "[[100-pi-subagent-read-only-attach-view-implementation|Pi subagent read-only attach view]]"
|
||||
blocked-by:
|
||||
- "[[100-pi-subagent-read-only-attach-view-implementation|Pi subagent read-only attach view]]"
|
||||
tags:
|
||||
- ticket/implementation
|
||||
---
|
||||
|
||||
# Pi subagent selectable monitor
|
||||
|
||||
## Question
|
||||
|
||||
Implement selecting a subagent from the expanded monitor and attaching to it without requiring the human to copy an id into `/subagent-attach`.
|
||||
|
||||
## What to build
|
||||
|
||||
The expanded subagent UI should support a selectable mode for visible subagent rows.
|
||||
The human should be able to move selection between subagents, see which row is selected, and attach to the selected child with a simple activation key.
|
||||
The existing `/subagent-attach <id>` command may remain as a fallback, but the primary interaction should be selection from the expanded monitor.
|
||||
The interaction should not add a text input path to the child and should preserve the read-only attached view behavior that already exists.
|
||||
|
||||
## Acceptance criteria
|
||||
|
||||
- [ ] Expanded subagent UI has a visible selected row when visible children exist.
|
||||
- [ ] Keyboard navigation can move the selection between visible subagents.
|
||||
- [ ] Activating the selected row opens the existing read-only attached child view.
|
||||
- [ ] Detaching from the attached child view returns to the parent session without losing the monitor state.
|
||||
- [ ] `/subagent-attach <id>` remains available as a fallback.
|
||||
- [ ] Tests or documented manual verification cover selection, activation, and detach behavior.
|
||||
|
||||
## Implementation Notes
|
||||
|
||||
This fixes the gap between the approved design's word "selecting" and the first attach implementation, which only exposed an id-based command.
|
||||
Prefer a Pi-native custom widget or overlay interaction that works with the existing monitor and attach-view code.
|
||||
Reference in New Issue
Block a user