Skip to main content
Live view shows a phone’s screen while its session is active. The Dashboard includes the live phone in its session viewer. Direct allocations through the CLI, SDKs, and REST API also return a hosted live_view_url unless you disable live view. The default hosted URL is interactive. Pointer and keyboard input reach the phone. Use a recording after the session ends.

Open an active phone

  1. Open Sessions.
  2. Select an active session or click Allocate A Phone to start one.
  3. Use the phone on the left side of the SESSION VIEWER. The Dashboard connects with your signed-in organization membership and reconnects the stream when needed.
The Dashboard does not expose the hosted viewer URL or its embed options. Use an SDK or the REST API when another application needs the URL.

Mint a fresh viewer URL

If you no longer have the allocation response, mint a fresh URL for an active session. The Dashboard manages its connection automatically. The CLI does not expose this operation.
This operation preserves the session’s allocation-time view_only and disabled settings. It refuses inactive sessions, sessions outside your organization, and sessions whose live view was disabled. Its response is a bearer viewer URL even when the original allocation used organization authentication. Minting a new URL does not revoke an older one.

Choose authentication and input behavior

The Dashboard and CLI use the default interactive viewer behavior and do not expose these allocation options. Configure them with an SDK or REST:
Use organization authentication for links shared inside your team. Third-party iframe cookie policies can prevent signed-in organization mode from working inside your product, so use token mode for end-user embeds.

Embed the viewer

The hosted page is chrome-less and iframe-embeddable:
The stream starts muted so it can render under browser autoplay policies. If your app sets a Content-Security-Policy, allow the hosted page and its realtime connection:

Keyboard focus

Browsers deliver keystrokes to an iframe only while it has focus. Safari requires a user action before it focuses a cross-origin iframe. Focus it from a click handler:
Pointer input does not require this step.

Appearance

The default is the bare phone screen on a transparent background. Query parameters customize the surround:

Protect capability URLs

Anyone with a bearer live_view_url can watch the phone and—unless the session is view-only—interact with it until the session ends. This includes the allocation URL in token mode and every URL returned by the token operation.
  • Do not log the URL or send it to analytics.
  • Prefer view_only=True for audiences that should not control the phone.
  • Prefer auth="org" for internal sharing that should require membership.
  • If you expose a token-mode URL, end the session. The URL stops working when the session ends.
Release directly allocated phones when you finish. Closing the viewer does not release the phone.

Next steps

Live Telemetry

Follow what the session is doing while you watch.

Recordings

Replay a session after it ends.

Retrieve Telemetry

Inspect its retained timeline and logs.