Authentication
Connect the CLI to your Browserless account by storing your API token locally.
The token is stored in your OS keychain (macOS Keychain, libsecret on Linux, DPAPI on Windows) and falls back to a mode-0600 file at ~/.browserless/config.json.
Command: browserless auth <subcommand>
Subcommands
login [token]Store your API token. Accepts a positional argument or stdin (echo $TOKEN | browserless auth login). Omitting the argument and piping from stdin keeps the token out of your shell history.statusPrint the current identity and where the token is stored.logoutWipe credentials from both keychain and config file.
Examples
Log in with a token
browserless auth login bless_abc123def456
Check auth status
browserless auth status
Authenticated
Token stored in: keychain
Server: https://production-sfo.browserless.io
Token resolution
When a command needs authentication, the CLI checks these sources in order:
--tokenflagBROWSERLESS_TOKENenvironment variable- OS keychain (keyed by server URL, so credentials for multiple regions coexist)
~/.browserless/config.json(mode 0600 fallback)
If none resolve, the command exits with code 3.