What a browser session is
A browser session has a name and a URL, often a service's stable URL. Configure them on the project and every workspace inherits them; attach as many as a workspace needs.
A browser session is a URL you want one focus away while a workspace is running, your local app, an admin page, a PR, a runbook.
A browser session has a name and a URL, often a service's stable URL. Configure them on the project and every workspace inherits them; attach as many as a workspace needs.
Spaces opens and focuses tabs through the macOS Automation permission, “Spaces wants to control Google Chrome”. If Chrome is not installed or the permission was denied, focusing a session shows an error naming Chrome instead of opening the URL. See Troubleshooting if the permission prompt never appears or was denied by mistake.
Stopping or deleting a workspace closes its tabs, whether you do it on the Mac, on the iPhone, or from the CLI, and whichever device the workspace lives on. The Mac app closes them when it sees the workspace stop or go away, so a workspace stopped while the app isn't running leaves its tabs open until you delete it. Restarting a workspace keeps its tabs open.
A browser session opens inside the app's own browser, with back, forward, reload, and Screenshot controls. Screenshot captures the visible view and opens it in Markup for annotation; the resulting image can then be attached from a terminal's message composer. This works for a remote Linux workspace too, as long as your phone is paired with the device that owns the workspace. If the service is not running yet, the row shows an error naming the service instead of a blank page.
Cookies and local storage stay isolated per service, the same way they do in Chrome on the Mac. See SPACES_<SERVICE>_URL in Environment variables for how a session's URL is built.