Skip to content
This repository was archived by the owner on Aug 17, 2026. It is now read-only.
This repository was archived by the owner on Aug 17, 2026. It is now read-only.

design: vibe_* live worker TV-wall surface #124

Description

@joeshull

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.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

  1. One session-level vibe panel vs per-tool-call cards that project into a shared wall?
  2. Does tool_execution_update.details already carry enough screen snapshots, or is a new event channel required?
  3. How do spawn/send/wait/kill/list share identity (worker id) across tool rows?
  4. 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.

Pointers

  • @oh-my-pi/pi-coding-agent/src/tools/vibe.ts (~77–93, 161–191, 482–593)
  • Dashboard analog: AgentToolRenderer + subagent map in event-reducer.ts

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions