-
Notifications
You must be signed in to change notification settings - Fork 0
v0.9.16: inline working card widget in the chat stream #381
Copy link
Copy link
Closed
Labels
area:conversationPublic transcript, host conversation, and internal delegation visibilityPublic transcript, host conversation, and internal delegation visibilityarea:tuiFull-screen terminal UI and ratatui consoleFull-screen terminal UI and ratatui consoleenhancementNew feature or requestNew feature or requestpriority:highTruth-in-advertising or locked-spec gapTruth-in-advertising or locked-spec gapsize:M1-3 days1-3 daysstatus:needs-designPending design decision, do not implementPending design decision, do not implementtype:featNew feature for v0.5 virtual teamNew feature for v0.5 virtual team
Metadata
Metadata
Assignees
Labels
area:conversationPublic transcript, host conversation, and internal delegation visibilityPublic transcript, host conversation, and internal delegation visibilityarea:tuiFull-screen terminal UI and ratatui consoleFull-screen terminal UI and ratatui consoleenhancementNew feature or requestNew feature or requestpriority:highTruth-in-advertising or locked-spec gapTruth-in-advertising or locked-spec gapsize:M1-3 days1-3 daysstatus:needs-designPending design decision, do not implementPending design decision, do not implementtype:featNew feature for v0.5 virtual teamNew feature for v0.5 virtual team
Context
Per umbrella
#377and ADR#378, sub-agent activity moves out of the right rail and into the chat stream as inline working cards. This issue lands the working card widget itself, fed by the lifecycle data from#380.Goal
Render each
Working-state spawn instance as an inline card in the chat stream, at the chat-time position where it was spawned.Required Visual (per ADR mockup)
✓; in-progress uses∴. Latest N lines visible (N is a config knob, default = 3 — anything older scrolls within the card region if naturally bounded by terminal width).__ISSUE_G__).Acceptance Criteria
WorkingCardrenders oneWorkingspawn instance per the visual above. The widget reads from the lifecycle record only — no kernel direct access.@rolementions in scrollback).Out of Scope
__ISSUE_G__).DoneandReportedrendering (__ISSUE_E__).__ISSUE_F__).__ISSUE_I__).__ISSUE_H__).Required Evidence
@host→ one sub-role working card with at least 2 tool calls.