design: computer tool live desktop session

[joeshull]

Child of #135

Needs a design session. Persistent desktop session + screenshots, not a result card.

Problem

computer executes against one live desktop session and records screenshot state (computer.ts ~103–104, 156–180). TUI has computerToolRenderer. Dashboard would Generic-dump args.

A useful surface is a session viewer (last frame, action log), not JSON.

Design questions

1. Reuse canvas / image-lightbox / live-server split, or a new computer pane?
2. Is tool_execution_update + images enough, or does the host need a screenshot stream?
3. Security: remote desktop actions from the web client — confirm/gate?

Pointers

• @oh-my-pi/pi-coding-agent/src/tools/computer.ts
• src/tools/computer-renderer.ts
• Dashboard: ToolResultImages.tsx, canvas driver

[joeshull]

Parent: #117.

[joeshull]

Proposal (unreviewed)

Draft from design session. Not locked.

Rec

A. Dedicated ComputerToolRenderer on the existing tool card: action = submitted code, last screenshot via ToolResultImages + lightbox. No remote-desktop input.

Approaches

• A (rec): card + existing images/lightbox
• B: persistent computer pane
• C: screenshot stream + new WS

Locked answers (proposed)

1. Reuse tool-card image/lightbox. Not canvas, not a new pane
2. No screenshot stream. Terminal last frame is enough
3. No web-client desktop control. Read-only

UX

display-only. Clickable last screenshot. No pointer/keyboard.

Out

No desktop pane, no stream, no permission/approval changes. #121 remains the only blocking input host.

[joeshull]

Locked: A

ComputerToolRenderer on the existing tool card: action = submitted code, last screenshot via ToolResultImages + lightbox.

No web desktop control. No screenshot stream. No new pane.