> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orchestrahq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Live sessions in the browser

> On a Local team, see which agent sessions are running on teammates' laptops, watch one and message its agent from the web app, end to end encrypted, with nothing stored by Orchestra

On a Local team, your teammates' agent sessions run on their own laptops, and
their transcripts stay there. The web app can still show what is running right
now. Your browser joins your team's relay as a device of its own, the same way
a laptop does, and each teammate's laptop streams its live sessions to it,
encrypted so that only your browser can read them. Orchestra stores none of it.

This page explains what you see, who decides what you can see, and what your
browser keeps.

## What you see

To open your Local team in the web app, choose your workspace's name at the top
left, then **Open in browser** under your team. Choosing the team itself opens
it in the desktop app, as before. This works on any computer or phone you can
sign in on.

The team's **Sessions** page shows **Live now** above the list whenever a
teammate's laptop, or another computer of yours, is connected:

* Each agent session running on a teammate's laptop, with who runs it, the
  agent (Claude Code, Codex and others) and how long it has been running.
* Its title, repository and the files the agent is working in, when that
  teammate shares the session with you (see below). Otherwise the row says only
  that a session of that agent is running, with **details not shared with you**.
* A session running on one of your own computers, marked **You**. You can watch
  and steer it from the browser too, the same as from that computer: handy for
  following your own agent from your phone.

Choose a shared session to **watch** it. The page streams the conversation as
it happens, in the same layout as any other session, marked **Live**, with a
line saying what the agent is doing now.

If the teammate lets you steer, a message box sits under the conversation.
What you send is handed to the agent at its next turn, attributed to you, just
like a message from a teammate's terminal. If they let you watch only, there is
no message box.

## Who decides what you see

Every decision is made on the laptop the session runs on, by that teammate's
own rules, at the moment you ask. Neither Orchestra nor the relay decides it.

| Your teammate's setting | What Live now shows you | Can you watch? | Can you message the agent? |
| - | - | - | - |
| The team default (nothing set) | Title, repository and files | Yes | Yes |
| Default changed to watch only, or you are listed to watch | Title, repository and files | Yes | No |
| Default turned off, or you are blocked | Only that a session is running | No | No |
| A private session | Nothing at all | No | No |
| Your own session, on another computer of yours | Title, repository and files | Yes | Yes |

A private session is not shown or joinable from any browser, yours included.
These are the same rules that decide who may join a session from a terminal
(see [Steering a session together](https://docs.orchestrahq.ai/multiplayer-sessions.md) and
[Session privacy](https://docs.orchestrahq.ai/session-privacy.md)). A change applies at once: block someone
and their Live now drops the details, and anyone watching who is no longer
allowed is taken out.

## What your browser keeps

* **A device key.** The first time a page needs it, your browser makes an
  encryption key pair. The private half is marked so that no script can read
  it out, not even Orchestra's own, and it stays in your browser's storage for
  this site. Only the public half is sent to Orchestra, under your sign-in, so
  teammates' laptops can encrypt to it. You get one key per workspace.
* **Nothing of the sessions.** What a laptop streams is opened in the open tab
  and held in its memory only. When the session ends, the laptop goes offline,
  you are taken out or you leave the page, it is gone, and the page says that
  nothing was kept.

Signing out of the web app removes the key from Orchestra and deletes every
key from the browser. If you are removed from the team, your browser is cut
off at once and deletes its key the next time it notices.

## When Live now does not show

| What you see | Why | What to do |
| - | - | - |
| No **Live now** at all | No other computer of the team is connected right now, or the web is showing a Cloud workspace | Open your team with **Open in browser**; Live now appears when a teammate's laptop connects |
| "This browser cannot hold an encrypted device key" | The browser has no support for the key type, or it blocks site storage (some private windows) | Update the browser, use a normal window, or use the desktop app |
| "This browser is no longer a device of the team" | You were removed from the team, or signed out elsewhere | Sign in again; ask a team admin if you were removed |
| "The laptop went offline" | The teammate's laptop slept, lost its network, or closed Orchestra | Try again when it is back |
| "You cannot watch this session" | The teammate's rules do not let you join it | Ask them to allow you |

## The trust you place in the web page

End to end encryption in a web page has one limit the laptop apps do not:
the page's code is served by Orchestra each time you open it. Your browser's
device is only as trustworthy as that code. If you need to rule that out,
watch from the [desktop app](https://docs.orchestrahq.ai/install-desktop.md) or the
[terminal client](https://docs.orchestrahq.ai/terminal-client.md) instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.