UI Interview - V1 Operator Console

Review-state branch packet and visual mockup for the dense desktop Operator Console variation.

Interview stage: `$ui-interview v1-operator-console`, full UI branch-review mode. Stage-zero interrogation completed over two rounds. The current round-2 checkpoint confirmed coverage is complete enough to advance into this UI packet and alignment review.

Interview provenance: live-ui-interview. This page is a pre-approval review surface. It does not write canonical `design/ui-v1-operator-console.md`, the interview log, or flow-tree decision metadata until final compiled YAML approval is provided.

Review Summary

Branch
v1-operator-console

Dense data table, persistent split-pane, inline launch row, desktop-dense posture.

Decision Needed
Approve, request another iteration, or reject this UI experiment branch.
Approval Boundary
Approval validates this branch for later prototype screen building. It is not production implementation approval.

Visual Mockup

The mockup renders the intended desktop-dense posture directly. Source artifact: research/_working/ui-interview-v1-operator-console-mockup.html.

Interactive review rendering - fixture data only, no external assets or iframe
gblock console New AgentKQR...
sort: status priority tunnel healthy
StatusNameToolRepoElapsedTokensStdoutActions
+ New Agent: repo / tool / prompt, then Cmd+Enter

Source Evidence

#SourceWhat it providesConfidence
E1design/ux-variations-monitoring-start/v1-operator-console.mdPrimary V1 UX variation spec: dense table, split-pane detail, inline launch row, keyboard model, responsive degrade, and prototype scope.High
E2design/flow-tree-personal-workstation.yamlFlow-tree state and sibling branch metadata.High
E3design/ux-variations-monitoring-start.mdSibling comparison and shared branch axes.High
E4design/_working/ux-variations-monitoring-start-brief.mdShared reframe: two-layer surface, folded tool-adaptive detail, all-web PWA.High
E5interrogation/ui-interview-r1-v1-operator-console.htmlRound-1 assumptions and open UI questions.High
E6interrogation/ui-interview-r2-v1-operator-console.html + sidecarCoverage checkpoint confirmed complete.High
E7design/ui-v2-card-mosaic.mdConfirmed sibling/control branch and approval triage caution.High

Assumptions Manifest

IDSourceAssumptionDecision
A1specV1 is the desktop-dense Operator Console branch for 8-12 concurrent agents.Confirmed
A2spec + briefS3, S4, and folded S5/S6 collapse into one persistent console route with table plus split-pane.Confirmed
A3specDense table, persistent split-pane, inline launch row plus command palette, and desktop-dense posture are fixed for this proposal.Confirmed
A4briefDetail is tool-adaptive, with no user-facing Mode A/B toggle.Confirmed
A5research + specSingle-user personal workstation; no sharing, collaboration, team permissions, or multi-tenant admin UI.Confirmed
A6prompt + checkpointCoverage is complete enough to build this packet and handle remaining issues as alignment feedback.Confirmed

Rendered UI Packet

Parent Flow and Coordination

V1 belongs to monitoring-start, covering the board-monitoring and one-click-start path. It is measured against the already approved V2 control branch and the still-proposed V3/V4/V5 siblings.

Touched flows are approval, recovery, device handoff, diff review, and settings. The V2 approval-triage finding carries forward: V1 can show inline and next approval actions, but blind global approval remains out of scope.

Page Inventory

SurfaceRoute / formPurposeSuccess condition
S3 Console tableSingle persistent console routeScan, sort, filter, and triage the fleet.User identifies waiting, error, and running agents across 8-12 rows in one glance.
S4 Inline launchPinned editable top row plus command paletteStart another agent without hiding the fleet.New starting row appears from valid repo, tool, and prompt.
Folded S5/S6 DetailRight split-pane bound by selected rowWork one agent while keeping the fleet visible.User steers the selected agent and still notices other rows changing.
Mobile degradeStacked list plus full-screen detail sheetPreserve monitoring and approval on phone.User can approve, inspect, and hand off to desktop.
Empty stateSingle centered start surfaceTeach vocabulary before rows exist.User launches first agent without empty table intimidation.

Layout and Navigation

Components and Controls

Fleet Table; Row Cursor; Status Badge; Status Count Chips; Global Table Search; Repo/Tool/Status Filters; Sort Selector; Inline Launch Row; Command Palette; Split Pane; Tool-Adaptive Detail; Terminal Renderer; Structured Stream Renderer; Prompt Injection Footer; Approval Inline Actions; Diff Micro-preview; Guarded Stop; Retry/Restart; Recap Strip; Connection/Tunnel Banner; Empty Console State; QR/Open-on-Mobile; Mobile Stacked Agent Row; Full-screen Mobile Detail Sheet.

ControlBehavior
New Agent rowExpands pinned row into launch inputs; Esc cancels; Cmd+Enter submits.
Command paletteKeyboard launcher for new agent, jump, filter, sort, next approval, and selected-row actions.
Global searchFilters visible rows across agent name, repository, tool, status, and stdout/stream text; combines with repo/tool/status filters.
Row selectionBinds row to right detail pane without navigating away.
Row action cellPerforms contextual action without changing current detail selection.
ApproveExpands diff peek or confirmation; final confirm resumes row and advances cursor to next waiting row.
RejectOpens inline reason input before sending feedback.
StopArm-confirm within 3 seconds for mouse and keyboard.
Retry / RestartRetries failed agent with same prompt or adjusted prompt from detail.
Pop-out detailGives terminal full width while preserving selected agent and route.
QR / Open on MobileGenerates short-lived handoff link with current selection encoded.

States and Accessibility

States covered: empty, loading repos, launching, starting, running, waiting, error, paused, idle, done, backend unreachable, tunnel reconnecting, credential expired, OAuth expired, disk warning, browser reconnect, concurrent-device update, hover, focus, selected, disabled, validation error, success, and reduced motion.

Accessibility is baseline: visible focus rings, logical keyboard order, non-color-only state labels, 44px mobile targets, reduced-motion support, icon labels/tooltips, and table semantics that survive virtualization.

Prototype Boundary and Batch Plan

  1. Batch S3: console shell, header, toolbar, populated dense table, status chips, selected-row styling.
  2. Batch S4: inline launch row, validation, loading/launching/error states, command-palette equivalent.
  3. Batch S5/S6: split-pane detail, CLI terminal fixture, API structured fixture, prompt footer.
  4. Batch States: approval diff peek, guarded stop, retry, backend/tunnel/credential banners, empty state.
  5. Batch Responsive: tablet column shedding and mobile stacked-list/detail-sheet degrade.

Coverage Checkpoint

Review risks: dense table intimidation, one-line stdout lossiness, mobile degrade acceptance, and split-pane terminal crampedness.

Proposed Canonical Destinations

These files are proposed only. They are not written until final approval YAML is consumed.

Approval Gates

Gate A - Interview Provenance

Do you accept that this packet is based on a completed live UI-interview checkpoint?

Gate B - V1 Mockup Direction

Is the dense table plus split-pane mockup a valid V1 Operator Console branch direction?

Gate C - Artifact Destinations

If approved, should the proposed canonical file destinations and flow-tree update be used?

Gate D - Missing Coverage

Is any decision-critical UI coverage missing before canonical approval?

Compile Responses

Answer one or more gates, then compile YAML. Complete approval requires all gates answered with no unresolved revision request.