You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 17, 2026. It is now read-only.
Needs a design session.vibe_* is one live multi-worker surface, not five cards.
Problem
TUI vibe renderer is a persistent worker “TV wall” (vibe.ts spawn/send/wait/kill/list). vibe_wait streams 500ms interim screen snapshots. A completed-result Generic card is not the product.
Dashboard has no worker-session store analogous to subagents.
Design questions
One session-level vibe panel vs per-tool-call cards that project into a shared wall?
Does tool_execution_update.details already carry enough screen snapshots, or is a new event channel required?
How do spawn/send/wait/kill/list share identity (worker id) across tool rows?
Parity target: TUI TV wall, or a thinner list + last-screen?
Tools in this issue
vibe_spawn, vibe_send, vibe_wait, vibe_kill, vibe_list — one session, do not split.
Child of #135
Needs a design session.
vibe_*is one live multi-worker surface, not five cards.Problem
TUI vibe renderer is a persistent worker “TV wall” (
vibe.tsspawn/send/wait/kill/list).vibe_waitstreams 500ms interim screen snapshots. A completed-result Generic card is not the product.Dashboard has no worker-session store analogous to
subagents.Design questions
tool_execution_update.detailsalready carry enough screen snapshots, or is a new event channel required?Tools in this issue
vibe_spawn,vibe_send,vibe_wait,vibe_kill,vibe_list— one session, do not split.Pointers
@oh-my-pi/pi-coding-agent/src/tools/vibe.ts(~77–93, 161–191, 482–593)AgentToolRenderer+ subagent map inevent-reducer.ts