Your browser workspace

Expand a browser, return to the grid, and keep shared access in your account.

One workspace, two viewing sizes

/browsers is your multi-browser grid. Click a preview and that browser expands edge-to-edge, like a video player. The URL becomes /browsers/{browserId}, but the same workspace and grid remain mounted underneath. Minimize or press Escape to return to the grid (Shift+Escape when the desktop has keyboard focus); Back/Forward restore the corresponding viewing size. Direct links and refresh also open the expanded viewer.

Grid filters, layout and scroll position survive expansion. Fullscreen means the application viewport; using the operating system’s Fullscreen API is not required. Switching viewing size must not pause, resume, fork or create a browser.

Live View links enter the same player

1. A sender creates a Live View URL: https://cloudbrowser.tv/view/{linkId}#share=….
2. The account shell validates the invitation, signs the recipient in, and adds a saved access relationship to that account’s browser library. The local preview simulates this with “Continue as Jamie”.
3. The browser opens fullscreen at its account-only /browsers/{browserId} URL. Minimize to see it alongside your own browsers in the same grid. Shared browsers show the sender’s avatar; your own browsers show a private or shared icon without your avatar.

Never place the share secret into OAuth state or a login return URL. In production, remove the fragment immediately and exchange it for a server-side pending acceptance handle bound to the login transaction. After sign-in, complete the authorized acceptance. The account-only viewing URL itself is not a transferable sharing credential.

Added to your account does not mean owned by you

The same browser is referenced, not copied. Its owner retains ownership and compute charges; it does not consume the recipient’s browser concurrency quota. Deduplicate repeated acceptance by account/browser and keep the specific source grant. Do not combine permissions from unrelated links or silently turn a shared record into an owned resource.

There are no separate ownership tabs or Live View links sidebar. Select the private/shared icon on an owned browser to manage its links, permissions, expiration and active sessions in place.

Permission changes remain authoritative

The library entry is a reference to current authorization, not a permanent copy of the permission at invitation time. Expiration, revocation, issuer access removal or browser deletion stops both grid previews and expanded viewing. Keep an unavailable card without revealing its old private screen. A paused browser shows only a clearly labeled, authorized last frame and cannot be resumed by a recipient.

A reusable share can be accepted by multiple accounts. A one-time invitation can be claimed once; successful acceptance binds access to that account. The accepted account can later request fresh runtime tickets without replaying the original invitation, while the parent authorization remains valid. Removing that access requires a valid invitation to add it again.

Preview subscriptions

Use low-bandwidth previews for visible grid cards and an interactive stream for the expanded browser. Stop offscreen subscriptions, reduce background-tab activity, and reuse authorized sessions when switching size. All preview and input channels must check the same account, browser and grant; changing size must never widen access. The application shell stays on cloudbrowser.tv; the isolated transport viewer at view.cloudbrowser.tv receives only a short-lived ticket through a strictly origin-checked handshake.

cloudbrowser auth login
cloudbrowser library add --url "$LIVE_VIEW_URL"
cloudbrowser library list --source shared
cloudbrowser library view br_shared
cloudbrowser library remove br_shared --yes

The backend stores browsers and accepted shares in PostgreSQL. Viewer credentials stay in HttpOnly cookies; share tokens are never persisted in localStorage. Auth0 handles sign-in; pending share acceptance is encrypted on the server and bound to the login transaction.