Public BYOK release · v0.1.0

Let your agent install Browser Bolt.

Copy this prompt into Codex or Claude Code. It checks for an existing install, downloads the pinned release and dependencies if needed, then verifies the MCP and browser connection separately. Start with one OpenRouter key. Add a Cerebras key for direct Qwen field writing.

View instructions

Installation and connection checks make no paid model calls. A browser connection is a separate setup step.

Open-source GitHub repo Valente Labs

Direct install

One command to install.

Already have uv? Install the public tagged MCP server and its declared dependencies in an isolated environment. The agent prompt checks what is already installed, connects it to your host, and checks browser readiness. The released default uses OpenRouter; a Cerebras key adds direct Qwen field writing.

uv tool install --python 3.12 --with-executables-from browser-harness 'jev-qwerebras-ultrafast[mcp] @ https://github.com/valente-labs/browser-bolt/releases/download/v0.1.0/jev_qwerebras_ultrafast-0.1.0-py3-none-any.whl#sha256=63db63a0ad8983f5b11b03a5633c3dd148d88b2c2ef405cd513fb8e1ce187902'

Connect your MCP client

One connection step for your tool.

Claude Code

claude mcp add --scope project browser-bolt -- "$(uv tool dir --bin)/jev-qwerebras-mcp"

Codex desktop + CLI

The Codex CLI command writes user-level MCP configuration for local Codex clients. Start a new task after adding it.

codex mcp add browser-bolt -- "$(uv tool dir --bin)/jev-qwerebras-mcp"

Claude Desktop

Claude Desktop keeps a separate local MCP configuration. Ask your agent to connect it, or use Developer settings to merge this entry with the absolute installed path.

{"mcpServers":{"browser-bolt":{"command":"/absolute/path/to/jev-qwerebras-mcp","args":[]}}}

Claude Desktop setup

These steps register the decision MCP. Browser actions still need a connected browser tool or the packaged Browser Harness reference host. Add provider keys only through your local host environment or secret manager, never in a copied command.

The exact prompt

Paste once. Let the agent do the setup.

View public v0.1.0 release

# Install Browser Bolt in this project

You are the user's Codex or Claude Code agent. Do the setup on this machine and report what passed. Use only the published [v0.1.0 prerelease](https://github.com/valente-labs/browser-bolt/releases/tag/v0.1.0). Do not install a mutable branch, ask for a key in chat, write a key to config, or make a paid provider call during setup.

## 1. Install the package

Check `uv --version`, `uv tool list --show-paths`, and this project's existing MCP entry. If `uv` is missing, install it from the [official uv instructions](https://docs.astral.sh/uv/getting-started/installation/). Reuse a v0.1.0 tool only when its preflight passes and its installed `direct_url.json` points to the release wheel URL below before the `#sha256` fragment. Otherwise run this command; it selects Python 3.12, downloading it if needed, installs the package and declared dependencies in one isolated tool environment, and exposes the Browser Harness CLI:

```sh
uv tool install --python 3.12 --with-executables-from browser-harness 'jev-qwerebras-ultrafast[mcp] @ https://github.com/valente-labs/browser-bolt/releases/download/v0.1.0/jev_qwerebras_ultrafast-0.1.0-py3-none-any.whl#sha256=63db63a0ad8983f5b11b03a5633c3dd148d88b2c2ef405cd513fb8e1ce187902'
```

The URL pins the wheel's SHA-256; dependencies still resolve from the package index. The release [SHA256SUMS](https://github.com/valente-labs/browser-bolt/releases/download/v0.1.0/SHA256SUMS) file has SHA-256 `446c771f2a08606ebaa22f8e9b297e867c27c33868aaf188b3505df6b0ac64e0`. If `uv` rejects `--with-executables-from`, update `uv` and retry. Repair only a broken or unverified Browser Bolt tool by adding `--force` after `install`; leave unrelated tools alone.

From outside any Browser Bolt source checkout, locate the installed `jev-qwerebras-host` and `jev-qwerebras-mcp` with `uv tool dir --bin`. Use absolute paths if that bin directory is not on `PATH`; `uv tool update-shell` is an optional permanent fix. Run the absolute host path with `--preflight`. Require `ok:true`, three tools, nine profiles, `provider_calls:0`, and `browser:not contacted`. Check Browser Harness 0.1.13 with its absolute path in the bin directory. An older install may keep that command only at `$(uv tool dir)/jev-qwerebras-ultrafast/bin/browser-harness`. If the package or browser dependency check fails, repair the named tool and repeat. Preflight does not prove Chrome is connected.

## 2. Connect the current host

Register the absolute installed `jev-qwerebras-mcp` path for this project, preserving existing config:

- **Claude Code:** `claude mcp add --scope project browser-bolt -- <absolute-path-to-jev-qwerebras-mcp>`. Check `claude mcp get browser-bolt`. Claude may require approval of this project entry in an interactive session.
- **Codex desktop or CLI:** merge `[mcp_servers.browser-bolt]` with `command = "<absolute-path-to-jev-qwerebras-mcp>"` and `args = []` into this project's `.codex/config.toml`. Keep the project-local config out of Git. `codex mcp list` checks the entry. If a provider variable will be available to the Codex process, forward only its name, for example `env_vars = ["OPENROUTER_API_KEY"]`, not its value. A terminal export does not update a running Codex desktop app.
- **Claude Desktop, if requested:** it has separate MCP settings. Merge the same stdio command into `claude_desktop_config.json` without replacing other servers; then restart and verify in Connectors.

Start a fresh host task and call `browser-bolt.list_profiles`. A config listing alone is not proof of discovery. The MCP chooses among actions the host observed; it does not observe the page, click, or verify an outcome.

## 3. Check the browser, then keys

Use the current host's browser tool to observe a harmless local page, execute one action, and check the changed page state. If using the packaged reference host, run the absolute Browser Harness path found above with `doctor --json --require-existing-daemon` first. When it reports no connected browser, follow the [Browser Harness setup guide](https://github.com/browser-use/browser-harness/blob/main/install.md), connect a dedicated Chrome profile, and rerun doctor. Do not silently enable remote debugging on someone's primary authenticated profile. Do not run `jev-qwerebras-host --live` during keyless setup; it makes provider calls.

One `OPENROUTER_API_KEY` supports Jev decisions and Qwen text through OpenRouter. If `CEREBRAS_API_KEY` is also available, use direct Cerebras Qwen text. Check only whether keys are present in the host's local environment or secret manager; never print them. The user can create an [OpenRouter key](https://openrouter.ai/settings/keys) and optionally a [Cerebras key](https://inference-docs.cerebras.ai/console/api-keys). Restart the host after its environment changes. Do not create accounts or purchase credits.

Report four states separately: package installed, MCP discovered by a fresh host task, browser connected and action verified, and provider-backed task verified. The last state remains pending until the user authorizes a live call. If something fails, give its exact step and next action. The [MCP docs](https://github.com/valente-labs/browser-bolt/blob/v0.1.0/docs/MCP.md) cover profiles and host contracts.

The public v0.1.0 prerelease and its downloads are live. The direct TypeSafe Jev route is not part of v0.1.0.