roboomp
5b937511c4
The host used to ship the entire transcript inside a single welcome frame, so a multi-MB session spent the guest's 30s first-welcome timeout on the relay transfer itself: ~1.3 MB took ~3s, ~4.2 MB took ~12s, and ~13.6 MB never arrived before the guest gave up with 'timed out waiting for the host's welcome'. Bump COLLAB_PROTO to 2 and split the welcome: - welcome carries metadata only (header, state, agents, entryCount, readOnly) and lands in well under one second. - a train of snapshot-chunk frames (SNAPSHOT_CHUNK_BYTES = 512 KB, oversize entries ship alone) carries the transcript. Last chunk flips final: true; an empty snapshot still emits one final chunk. - the host queues welcome + chunks synchronously inside #handleHello, preserving the host comment's ordering invariant (later broadcast frames cannot interleave between them). - the TUI guest accumulates chunks under a SNAPSHOT_PROGRESS_TIMEOUT_MS that resets per chunk; only after final does it write the replica jsonl, switchSession, and render. The first-welcome timeout still guards arrival of the small welcome. - the collab-web GuestClient streams entries into the snapshot as chunks arrive and flips phase to 'live' on final. Includes a contract test (in-process relay) asserting the welcome is metadata-only, the chunk train fans the 1.5 MB synthetic transcript across multiple frames with only the last marked final, and the flattened entries match the source snapshot. Fixes #3144
@oh-my-pi/pi-wire
Shared TypeScript wire contracts for omp collab live sessions.
The package contains only JSON-safe protocol shapes and constants. It has no runtime dependencies and is consumed by both the host CLI (@oh-my-pi/pi-coding-agent) and browser guest (@oh-my-pi/collab-web).
Exports
import type { GuestFrame, HostFrame, SessionEntry } from "@oh-my-pi/pi-wire";
import { COLLAB_PROTO, DEFAULT_RELAY_URL, ENVELOPE_HEADER_LENGTH } from "@oh-my-pi/pi-wire";
Key groups:
- message and transcript entry shapes rendered by collab guests,
- live agent event and task-subagent bus payload shapes,
GuestFrame,HostFrame, andWireFrameunions for AES-GCM sealed payloads,- relay control TEXT messages,
- link/envelope constants shared by host, guest, and local relay code.
Protocol boundary
pi-wire does not encode, decode, validate, encrypt, or route frames. It defines the shared contract used at those boundaries:
- callers build a
GuestFrameorHostFrame, - transport code serializes it as JSON inside an encrypted payload,
- relay code routes opaque envelopes using the plaintext peer-id prefix,
- receivers switch on
frame.tand tolerate unknown future fields.
Keep protocol changes backward-aware: bump COLLAB_PROTO only when old hosts and guests must reject each other.