Share only what participants should see
Live Share lets participants receive terminal output from a shared session. Read-only access prevents typing; it does not hide output. Before sharing, close sensitive views and consider what the next command, scrollback or session snapshot may reveal.
Start a live share
- Open the intended terminal and choose Share.
- Choose Current Session.
- Select read-only access unless participants need to type.
- Review approval, invitation expiry, connection expiry and transport options offered by your deployment.
- Choose Start Sharing and send the invitation through a trusted channel.
- Monitor participants and end the share when the work is finished.
Review pending access requests in Share. Participants join as viewers. If you enabled typing for the room, use Grant control for the intended participant; only that controller can type. Use Reclaim control to return them to viewing. A display name or visible cursor does not grant permission.
Treat the complete invitation as a secret
Live terminal content is encrypted before it leaves the host. The invitation password is carried in the link's fragment rather than an ordinary request query. That protects it from being sent as part of the initial page request; it does not make a copied link safe to publish.
Browser history, clipboard managers, screenshots, extensions and recipients can still expose an invitation. Send the entire invitation only to intended participants. Do not paste it into public issues or support logs.
For a relay invitation, approval applies to the room, not to a verified personal identity. Anyone holding the current invitation and password may join while the room is approved. A requester's display name is self-reported.
For a sensitive session, confirm recipients separately and end the room when the intended collaboration is over. Do not assume approving a familiar name creates a non-transferable invitation for that person alone.
Enrolled direct invitations also require account sign-in and device confirmation. In the browser, choose Sign in and join when shown. If approval is required, the host approves the connecting device before it receives the terminal.
End access deliberately
Use Revoke Access & Disconnect to end the room and check the result. Revoking a participant from this Share dialog also ends the share for everyone. Expiry and revocation can prevent admission independently of the displayed participant name. An unconfirmed cutoff is not proof that every remote connection has stopped.
Ending the room cannot retract output already received, undo commands already run, or stop every detached process. A viewer reconnect must obtain current permission; interactive input is not meant to be replayed as an automatic recovery mechanism.
For ongoing access through an enrolled agent rather than a view of your current terminal, read delegated server access. For connection choices, see transports and fallback.