Collaboration & Presence

LeapMux keeps a workspace’s layout in sync across every client that has it open — your own browser tabs, windows, and devices, plus anyone you have shared it with. Open the same workspace in two places and its tiling tree, tabs, splits, and floating windows stay identical in both, in near-real-time. This is layout sync, not document co-editing: there is no shared text cursor and no co-typing in an agent chat or terminal.

Two facts shape everything below:

• Editing the layout is the owner’s job. Only the workspace owner can open, close, move, rename, split, or resize things — from any of their own clients. Live sync is, first and foremost, how your own tabs, windows, and devices stay in step.
• Sharing is read-only. People you share a workspace with get a live, read-only view: they watch the layout change as you work and can open each tab’s content over their own end-to-end-encrypted channel, but they cannot modify the layout. The Hub rejects layout edits from anyone but the owner.

What syncs

When a workspace is open in more than one client, these stay in step within roughly a frame to a network round-trip:

• The tiling tree — splits, grids, and leaf tiles, including dragging a divider to resize.
• Tabs — agent, terminal, and file tabs: whether they exist, their order, which tile they live in, and which Worker hosts them.
• Floating windows — position, size, opacity, and the tiles inside them.
• Workspace lifecycle — creating, renaming, or deleting a workspace updates the sidebar everywhere.
• Tab titles and file-tab paths — these ride the Worker’s end-to-end-encrypted channel rather than the layout channel, so the Hub never sees them.

For the layout primitives themselves, see Tabs & Layout; for the sharing controls, see Workspaces.

Your own devices and tabs

The common case is one person, several clients. Open a workspace on your laptop and your phone, or in two browser tabs, and a split or tab you create in one shows up in the others. There is nothing to set up — no session to start, no link to share, no toggle; sync is always on. Your edits apply optimistically, appearing instantly before the Hub confirms them.

If two of your own clients change the same thing at the same instant, LeapMux resolves it automatically: last write wins, with no merge prompt, and every client converges on the same result. You will rarely notice it happen.

Presence: who hears the turn-end sound

LeapMux tracks one presence fact per workspace: which client is active — the one that most recently received your keyboard, pointer, or scroll input. It exists for a single purpose: when an agent finishes a turn, only the active client plays the notification sound, so the same agent doesn’t ding on every open tab and device at once. Other clients viewing that workspace stay silent. (If no clear active client can be determined, LeapMux plays the sound rather than risk swallowing it.)

You don’t choose the active client — it follows wherever you last interacted. To keep a particular client quiet regardless, set Turn End Sound to None in its Preferences dialog (see Settings & Preferences). The sound is also skipped for trivial single-exchange turns and rate-limited so it can’t fire repeatedly.

Note: All tabs and windows of one browser profile count as a single client, because they share one login session — so they never compete for the ding among themselves. A separate browser, another device, or a CLI token is a distinct client.

There are no other presence features — no avatars, “who’s viewing” badges, remote cursors, or typing indicators.

Who can see a workspace

You see — and sync — only the workspaces you can read: ones you own, and ones another user has explicitly shared with you. Being in the same organization grants nothing on its own, and a newly shared workspace appears in your sidebar automatically. To grant or revoke access see Workspaces; for roles see Organizations & Members.

A share grants a read-only view of the layout plus permission for the Hub to route your traffic to the workspace’s Workers; to actually read agent or terminal content, the recipient’s client opens its own end-to-end-encrypted channel to each Worker. The Hub relays workspace structure (tab positions, geometry, titles) but never agent transcripts, terminal I/O, or file contents — see Security & Threat Model.

Warning: The sharing dialog’s “All org members” option is not currently functional — the backend rejects it. Share with Specific members instead.

Solo mode

In solo mode there are no other users, so sharing is disabled and its controls are hidden. Layout sync across your own tabs and windows, and the turn-end sound, work exactly as described above. See Running LeapMux.

Troubleshooting

For broader diagnostics, see Troubleshooting.