The OMP Collab Workspace (located at /collab in the WebUI) provides a rich, integrated environment for interacting with your agent.
How it works (E2E Model)
OMP collaborative sessions are strictly end-to-end (E2E) encrypted.
- The agent hosts a session and outputs a link containing a room ID and a cryptographic key.
- The web guest client (usually
my.omp.sh) connects via a relay. - The decryption key is passed only via the URL
#fragment, meaning it is never sent to the server.
For a deeper dive into the underlying protocols, see the core collab.md harness doc.
WebUI Integration
Because rooms are ephemeral and encrypted, the local agent.db does not maintain a register of active rooms.
Instead, the WebUI provides a “paste-to-connect” experience:
- Link Parser: A robust parser (
lib/collab.ts) strips wrappers (omp join "...") and extracts the rawroomIdandkeyfrom various URL forms. - Access Modes: Based on the key length (48 bytes for Full Control, 32 bytes for View-only), the UI updates its badges and toolbar.
- Local Storage: The workspace saves recently connected rooms in the browser’s
localStorageto emulate a persistent session history without compromising the E2E guarantee. - The Embed: The UI mounts
my.omp.shsecurely inside a sandboxed<iframe>, injecting the specific room fragment required for connection.
Embedded Toolbar
When connected, the WebUI provides a native wrapper around the iframe featuring:
- Mode indicator badges.
- Copy Link / Open in new tab actions.
- Fullscreen mode.
- A seamless room-switcher via a drawer panel.