can1357
3ff65ead6b
- Bumped the collaborative protocol version (`COLLAB_PROTO`) from 2 to 3. - Required protocol-3 to coordinate `ui-request`, `ui-request-end`, and `ui-response` frames. - Rejected older protocol-2 guests at handshake to prevent host-asked requests from hanging. - Updated verification tests and CI installation check scripts to expect protocol version 3.
@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.