Get the live view and debugger URLs for a running Browserbase session and embed them read-only or interactively

Documented steps

1. Ensure the session is currently running - debug URLs are for live sessions, not completed ones. Reference: https://docs.browserbase.com/platform/browser/observability/session-live-view
2. Call the session debug endpoint at /v1/sessions/{id}/debug authenticated with X-BB-API-Key, or use the SDK: const links = await bb.sessions.debug(session.id).
3. Read the response fields: debuggerUrl (live view including browser chrome/borders), debuggerFullscreenUrl (no borders), wsUrl (WebSocket for real-time updates), and pages (array of per-tab objects, each with its own debuggerUrl and debuggerFullscreenUrl).
4. For a single-tab view use links.debuggerFullscreenUrl; for a multi-tab session pick the tab explicitly, e.g. links.pages[1].debuggerFullscreenUrl.
5. Embed the URL in an iframe with sandbox="allow-same-origin allow-scripts" and allow="clipboard-read; clipboard-write".
6. To make the embed read-only (observation, demos, audit), add CSS pointer-events: none to the iframe. To make it interactive so a human can click and type, omit that CSS - this is the only switch between the two modes.
7. Append &navbar=false to the live view URL to hide the navbar for a cleaner embed.
8. Set the session's browserSettings.viewport at creation (e.g. 360x800) if you want a mobile-shaped live view.
9. For human-in-the-loop flows, pair an interactive live view with browserSettings.solveCaptchas: false so a person can complete the challenge themselves.