Premium · v1 · July 2026
LiveShare
Two or more people, one live session. You send an invite code, they send one back, and the two apps connect straight to each other. Nothing reaches a Plexon server, not even the connection details. Your guest watches the AI respond as it happens; everyone sees who is in the room and who is driving, and the host admits guests, promotes them, pauses prompting, or removes anyone. Both apps have to reach each other directly, so the same network is the reliable case.
Two Codes, No Server
Open a session's menu, pick "Share live", and create an invite. Send the code however you already talk to each other. They paste it, send you the reply code their app shows, and you paste that back. That exchange IS the connection setup, which is why Plexon needs no server for any of it.
- Share live lives in the session overflow menu, next to Export and Share session file
- Send the code on WhatsApp, Slack, email, or scan the QR in person
- Nothing reaches a Plexon server, not even the connection details
- Each invite lets in one person, so it cannot be reused behind your back
Watch the AI Work, Together
Guests see the transcript update live, including tool activity as it runs, the same way the host sees it. The AI runs on the host machine with the host account, so there is a single payer and one source of truth. Everyone stays in sync as the response streams.
- Live token streaming, tool cards, and results mirror to every participant
- The host runs the turn; guests never consume an extra seat
- If the link drops, the guest keeps what they were reading and asks for a new invite
Turn-Taking Keeps It Sane
Only one AI turn runs at a time. While a response is streaming, other people can steer or interrupt, but they cannot start a competing turn. Everyone sees who is currently driving the AI, so there is no talking over each other.
- A single floor decides who prompts next
- Steer or interrupt an in-flight turn instead of racing it
- The host can pause guest prompting at any time
Safe by Default
Sharing a session lets a collaborator drive an agent that runs on your machine, so Plexon is cautious. Nobody gets in until you say so, and when someone connects you both see the same four safety words, so you can check on the phone that you are talking to the person you meant to. Guests then join read-only and can do nothing until you promote them.
- You admit each guest by hand; nothing is shared before you do
- Four safety words on both screens catch a code that was tampered with
- Guests default to Viewer; you promote to Driver deliberately
- File and shell output is hidden from guests
- Change a role, pause prompting, or remove a participant live
What Live Share Unlocks
One Live Session
Everyone works on the same running conversation, not a copy. Join from a link and see the AI respond as it happens.
No Server, Not Even a Handshake
The two apps talk straight to each other, end to end encrypted. Nothing about the session reaches Plexon, including the connection details. The trade is reach: both apps have to find each other, so the same network is the reliable case.
Real Time, No Collisions
Live streaming with turn-taking. One AI turn at a time, with steer and interrupt for everyone and a clear signal of who is driving.
You Stay in Control
Guests start read-only. Promote to Driver only when you trust them, and hidden tool output keeps a read from broadcasting a secret.
Connects to
Nothing here works alone. See the whole map for how the pieces fit together.
This one is taught in step 8 of 8: share it, or publish it.
Where it goes
This extends Session Sharing.
A .plexshare file is a finished session; Live Share is the running one.
Seen in these jobs