For Carbons & Silicons · API v1

Use Browser.
Build on Browser.

Managed browser profiles, shared sessions, live handoff, recordings, search, and fetch. Use the CLI for automation and the website for interactive work.

Read the full CLI guide or explore any command with --help.

1. Install with Silicon Apps

Install the Silicon Apps CLI, then install Browser and Accounts. Silicon Apps manages installed app updates.

silicon-apps install browser
silicon-apps install silicon-accounts
browser --help
browser accounts --json

2. Sign in with Silicon Accounts

On the Browser website, Carbons select Continue as Carbon and complete the hosted Accounts sign-in. Silicons hand Browser an app-specific short-lived token:

silicon-accounts login --app browser
browser login --slt TOKEN
browser login status --json

Replace TOKEN with the returned slt_ token, or paste it into Continue as Silicon on the website. A token works once and expires after two minutes. Browser never receives an STK.

3. Run a browser

browser profile ls
browser session new PROFILE_ID --name "Research" --description "Compare vendors" --ttl 30m
browser run SESSION_ID "open https://example.com"
browser run SESSION_ID "snapshot -i"
browser run SESSION_ID "screenshot ./research.png"
browser session end SESSION_ID --note "done"

Use browser profile new --help for a reusable profile, or browser session new --incognito for a fresh session. The website opens live browsers, profiles, recordings, usage, and command logs.

browser search "browser automation" --purpose "Find primary sources"
browser fetch https://example.com --purpose "Extract relevant claims"

Your account

Browser identifies you by your permanent Accounts UUID. Your c: or si: display handle can change without changing ownership. Profiles can grant access to other account UUIDs.

Website sign-ins are saved in this tab. Switching accounts keeps their data and credentials separate. If a refresh is interrupted, sign in again with a fresh token. Manage your identity and app access at Silicon Accounts.

Build on Browser

The Browser API uses /api/v1. Discover its Accounts application at GET /api/v1/accounts. Authenticated calls carry the JWT access token in Authorization: Bearer TOKEN and the fixed workspace header X-Org-Id: browser. Responses use {"data": ...}; failures return an error object.