To attach to a running Chrome instance on Windows:
```powershell
chrome.exe--remote-debugging-port=9222
dev-browser--connect
```
Windows npm installs download the native `dev-browser-windows-x64.exe` release asset during `postinstall`, and the generated npm shims invoke that executable directly.
After installing, just tell your agent to run `dev-browser --help` — the help output includes a full LLM usage guide with examples and API reference. No plugin or skill installation needed.
<summary>Allowing dev-browser in Claude Code without permission prompts</summary>
By default, Claude Code asks for approval each time it runs a bash command. You can pre-approve `dev-browser` so it runs without permission checks by adding it to the `allow` list in your settings.
**Per-project** — add to `.claude/settings.json` in your project root:
```json
{
"permissions":{
"allow":[
"Bash(dev-browser *)"
]
}
}
```
**Per-user (global)** — add to `~/.claude/settings.json`:
```json
{
"permissions":{
"allow":[
"Bash(dev-browser *)"
]
}
}
```
The pattern `Bash(dev-browser *)` matches any command starting with `dev-browser ` followed by arguments (e.g. `dev-browser --headless`, `dev-browser --connect`). This is safe because dev-browser scripts run in a sandboxed QuickJS WASM environment with no host filesystem or network access.
You can also allow related commands in the same list:
```json
{
"permissions":{
"allow":[
"Bash(dev-browser *)",
"Bash(npx dev-browser *)"
]
}
}
```
> **Tip:** If you've already been prompted and clicked "Always allow", Claude Code adds the specific command pattern automatically. The settings file approach lets you pre-approve it before the first run.
