The management app
The interface the daemon serves: the seven screens, what each one is for, and the settings that exist nowhere else because they belong to this machine rather than to your account.
The daemon serves a management interface, and the desktop client renders it. It does everything the REST API does, and it is the fastest way to see a profile before you point an agent at it.
Run the daemon binary on its own and the interface is at the daemon's own address. On a loopback bind the daemon prints that address on start with the token in the URL fragment, so the page signs itself in.
The seven screens
| Screen | What it is for |
|---|---|
| Activity | The landing screen: what is running right now, and what agents have been doing. See Activity & runs. |
| Profiles | The list, the create form, and one page per profile with its identity, credentials, tasks, memory and passkeys. |
| Presets | Templates for making many profiles at once, plus the video presets. |
| Videos | Recordings and rendered films. See Videos. |
| Proxies | The pool, with a check button per row. See Proxies & exits. |
| Mailboxes | Where confirmation codes arrive, and which profile is bound to which address. See Email inboxes. |
| Extensions | The daemon-wide library, and which profiles load what. See Extensions. |
Settings
Four tabs, and most of what is in them exists nowhere else, because these are decisions about this machine rather than about your account.
General carries the account this machine is signed in to, updates, the agent access card with the address and token to paste into an MCP client, remote access, and diagnostics.
Backup & security carries profile sync, the secret layer switch, and the exit rule switch.
Video carries the codec status, voice providers for narration, and the media library. See Videos.
Permissions carries the interruption rules: what happens when the browser itself asks something, such as a location prompt or a device chooser.
Two of these switches are deliberately local. Remote access and the exit rule sit on the machine, not in the portal, and the daemon reads its own switch on every beat rather than at startup.
If the cloud could open a tunnel into your machine, the trust boundary this whole product is built around would be gone. And a switch that only took effect after a restart is a switch people give up on.
What the interface deliberately does not show
The protection verdict. Every profile carries one, computed by the same functions the launch runs, and the API hands it out. The interface renders none of it: it is an operator's call, not a score to stare at, and the launch still fails closed on it either way.
A tool profile switch. Which MCP tools the daemon serves is read from its configuration at startup, and there is no route that widens the catalog at runtime. Changing it means editing the configuration and restarting.
The account lives elsewhere
Everything about the subscription is on scalebrowser.net, not here: plan and billing, which machines are paired, sessions, two-factor, API tokens for pairing, connectors for remote access, and account deletion.
The split is the same one the product runs on. The app manages browsers on your machine; the account manages what you are allowed to run and where. See Plans & limits and Machines & sign-in.
Next
- Quickstart: the five steps this interface is step two of.
- Profiles & personas: what the profile page is showing you.
- REST API: the same operations, without a mouse.