yoi/.yoi/tickets/open/20260605-210703-workspace-orchestration-panel/thread.md

Created

Created by LocalTicketBackend create.

---

Plan

Plan: design the workspace orchestration panel before implementation.

The panel is not a :ticket command extension. It is a workspace-scoped orchestration surface with:

• Companion foreground management chat;
• Ticket Intake composer target that sends user input directly to Intake, not Companion history;
• background workspace Orchestrator restored/spawned as <dir-name>-orchestrator;
• Intake -> Orchestrator handoff;
• an action model prioritizing human-required Ticket/Intake decisions over raw Pod idle state.

Implementation is split into child tickets:

1. workspace-orchestration-panel-design
2. workspace-panel-orchestrator-lifecycle
3. workspace-panel-composer-targets
4. ticket-intake-orchestrator-handoff
5. workspace-panel-action-model

Existing :ticket ... commands remain as low-level fallback, not the main UX.

---

Decision

Decision/update from UI discussion:

Do not preserve --multi as a separate long-term UI surface. The workspace panel should become the unified workspace view.

--multi-style Pod list behavior remains useful, but should be treated as the panel's no-Ticket / Pod-centric route rather than a distinct architecture. In workspaces where Ticket config/storage is unavailable or Ticket usage is not desired, opening the panel should still provide the current multi-Pod discovery/attach/send affordances as a fallback view.

Implications:

• Implementation can reuse current --multi code/components as the first panel substrate.
• The long-term command/launch model should prefer a panel view option; any existing --multi entry point can remain as a compatibility alias or shortcut into the Pod-centric panel route during migration.
• The panel model should tolerate an empty/unavailable Ticket backend and still show useful Pod rows/actions.
• Avoid designing two separate surfaces with duplicated selection, attach, send, and rendering logic.

---