Install Clawbrowser
The fastest path is to let clawctl configure the runtime and your agent integration. You can also install manually and connect over CDP from Playwright, Puppeteer, or your own agent.
Quick Start
Select your AI agent below. The install script configures Clawbrowser and wires it into your agent automatically.
Paste this prompt into Claude Code or Claude Desktop to install automatically.
Install Clawbrowser and clawctl by following the official Clawbrowser install documentation.
Primary docs:
- https://raw.githubusercontent.com/clawbrowser/clawbrowser/main/INSTALL.md
- https://github.com/clawbrowser/clawbrowser
Instructions:
1. Read INSTALL.md first.
2. Follow the documented installation flow exactly.
3. Start from the standalone clawctl archive for the current OS/arch.
4. Do not download the browser archive manually as the bootstrap path.
5. Do not download the portable runtime manually unless INSTALL.md explicitly documents that as an offline/pre-extracted runtime path.
6. Do not use npm, npx, curl-piped installers, or a raw source checkout as the install path.
7. Run clawctl install so it can install or reuse Clawbrowser and install the portable runtime when needed.
8. Use the documented target/integration selection from INSTALL.md.
9. After installation, verify the browser using the verification steps documented in INSTALL.md.
API key:
- First check ${XDG_CONFIG_HOME:-$HOME/.config}/clawbrowser/config.json.
- If api_key already exists, do not ask again.
- If api_key is missing, ask once for the real API key from https://app.clawbrowser.ai.
- Save it using the documented clawctl config command.
- Never store the API key in shell rc files, environment variables, MCP config, agent config, project files, or logs.
Expected result:
- Standalone clawctl is installed and available.
- clawctl install has completed successfully.
- Clawbrowser is installed or reused.
- The portable Linux runtime is installed only when the host requires it.
- The selected agent integration is configured according to INSTALL.md.
- clawctl start works.
- Browser verification passes according to INSTALL.md.
Agent installer
Run the installer for the agent you use. The command validates the local runtime, writes agent configuration, and returns structured status for automated setup.
clawctl install --agent codex --json
clawctl install --agent claude-code --json
clawctl install --agent claude-desktop --json
clawctl install --agent all --jsonManual quick start
Set your API key, start a named browser session, and pass the printed CDP endpoint to your automation tool.
export CLAWBROWSER_API_KEY=clawbrowser_xxxxx
clawbrowser start --session work -- https://example.com
clawbrowser endpoint --session workPlatforms
macOS supports desktop app workflows. Linux supports container and headless runtime workflows. Windows users can install clawctl and connect supported agents from the terminal.
For containerized setups, keep the API key and profile storage mounted in the environment where the agent runs.
Coming from Browserbase?
Clawbrowser moves the browser runtime from a hosted cloud service to your own machine or container. Review the differences in deployment, data residency, scaling, pricing, and fingerprint control before switching your CDP endpoint.