browserlisted

# Browser Automation Routes to specialized subskills based on the target. ## Routing Table | Target | Subskill | When to Use | |---|---|---| | Websites, web apps | `browser-use.md` | Any HTTP/HTTPS URL in a regular browser | | Electron desktop apps | `electron-use.md` | Attach to a running Electron process via CDP port | ## Which machine? (`--device`) The routing table above picks the *kind* of target. This picks the *box*. Every `agents browser` command takes `--device <host>`, which runs the CLI over there — so the target machine resolves its own profile. **Never pass `--profile` on a `--device` run**; you would be naming a profile that means something different on that box. The reason this matters is not display, it is credentials. A fleet usually has one browser carrying the real logins, and it lives on one machine. An agent on a worker that needs to act as the user (post, read a dashboard, use a signed-in API) has to reach that browser rather than launch a logged-out one locally. ```bash agents browser profiles logins # what is signed in here agents browser profiles logins --device <host> # ...and over there agents browser navigate --device <host> --url https://example.com ``` `agents browser profiles logins` is the discovery step: one row per detected session, with the profile name, the service, the signed-in account, and whether login credentials sit in that profile's secrets bundle. Read it to find which box holds the session you need be