Browse (the skill-based browser)

This is the platform's browser: the logic lives in this skill and runs in your shell; only the heavy runtime (browser-use + Chromium) is baked into your computer's image at /opt/browser-engine/venv. The browser itself is a remote stealth browser you drive over CDP, hosted by whichever provider the deployment configures. It is slow and expensive, for acting on a site, not reading one. To retrieve information (read a page, check a price, hit an API), reach for curl/wget first; browse only when you must interact, sign in, fill and submit forms, click through a flow, or when a plain fetch is genuinely blocked by heavy JS or a bot wall. (To verify a localhost site you built, don't use this at all, a remote browser can't reach your loopback; use the local headless chromium binary.)

Pick the provider

Which provider you use is decided by which API key is available in your env (or obtainable through the keychain). Org keys arrive automatically: an admin saves a provider's key as an org credential delivered as sandbox env (admin UI → Service credentials → delivery "Sandbox env"), and it rides into every all-internal conversation, nothing here is deploy config. A person's own keychain key overrides the org one. A provider can also be offered as a shared credential you call through QM's broker without ever holding the key; the provider doc says so when it supports that (Kernel does, via kernel). Keys you may see today:

Use the absolute directory reported by the skill read for all providers/ paths below. Keep the same explicit sandbox_id for the skill read and every execute command in this flow, including the runner.