can1357
ca85d9fe69
- Changed `DEFAULT_RELAY_URL` in `@oh-my-pi/pi-wire` from `wss://relay.omp.sh` to `wss://my.omp.sh` and updated the constants, collab-link, and join-command tests asserting the old origin. - Added `DEFAULT_SHARE_URL` (`https://my.omp.sh/s`) to pi-wire with its changelog entry; it shares a changed run with the relay constant and is consumed by the upcoming /share work. - Updated collab-web canonical/OG/twitter URLs in `index.html`, `robots.txt`, `sitemap.xml`, README, and the `local-relay.ts` doc comment to the new domain. - Refreshed the `/collab` entry in the coding-agent changelog to reference the new relay origin.
@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.