How do I install the Browser Use Install skill?

Run npx skillmds@latest add openbmb/browser-use-install in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Browser Use Install safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Browser Use Install?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Browser Use Install free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Browser Use Install?

OpenBMB (@openbmb) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Browser Use Install by openbmb — Agent Skill

Name: Browser Use Install
Author: OpenBMB

Browser Use Install

Use before browser-use, Playwright MCP, web browsing, browser automation, or when browser-use fails with a missing browser, missing executable, "Executable doesn't exist", or Chrome/Chromium install error in PilotDeck Desktop.

OpenBMB a1eba8e 2.2 KB Updated Sep 17, 2026

File contents

Browser-Use Install

PilotDeck Desktop ships browser-use without a bundled Chrome browser. When browser automation is needed, install the Playwright Chrome for Testing browser into the user's writable PilotDeck data directory, then retry the browser-use tool.

Install

Run this from any working directory:

node "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

In PowerShell, use:

node "$env:PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

If PILOTDECK_RUNTIME_ROOT is not set, find the PilotDeck runtime root first. It is the directory that contains node_modules/@playwright/mcp/cli.js and dist/src/cli/pilotdeck.js, then run:

PILOTDECK_RUNTIME_ROOT="/path/to/runtime" node "/path/to/runtime/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

PowerShell equivalent:

$env:PILOTDECK_RUNTIME_ROOT = 'C:\Path\To\PilotDeck\resources\runtime'
node "$env:PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

Mirrors And Offline

Use the same environment variables as desktop packaging when the default network is blocked:

PILOTDECK_DESKTOP_DOWNLOAD_MIRROR=china node "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

For fully offline installs, point to a directory containing the matching chrome-*.zip archive:

PILOTDECK_DESKTOP_PLAYWRIGHT_ARCHIVE_DIR="/path/to/playwright-archives" node "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"

After Install

Retry the browser-use request after the install succeeds. If the current MCP session still reports the old missing-browser error, tell the user to send the same request once more so PilotDeck can start a fresh browser-use session.

---name: browser-use-installdescription: Use before browser-use, Playwright MCP, web browsing, browser automation, or when browser-use fails with a missing browser, missing executable, "Executable doesn't exist", or Chrome/Chromium install error in PilotDeck Desktop.---# Browser-Use InstallPilotDeck Desktop ships browser-use without a bundled Chrome browser. When browser automation is needed, install the Playwright Chrome for Testing browser into the user's writable PilotDeck data directory, then retry the browser-use tool.## InstallRun this from any working directory:```bashnode "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```In PowerShell, use:```powershellnode "$env:PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```If `PILOTDECK_RUNTIME_ROOT` is not set, find the PilotDeck runtime root first. It is the directory that contains `node_modules/@playwright/mcp/cli.js` and `dist/src/cli/pilotdeck.js`, then run:```bashPILOTDECK_RUNTIME_ROOT="/path/to/runtime" node "/path/to/runtime/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```PowerShell equivalent:```powershell$env:PILOTDECK_RUNTIME_ROOT = 'C:\Path\To\PilotDeck\resources\runtime'node "$env:PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```## Mirrors And OfflineUse the same environment variables as desktop packaging when the default network is blocked:```bashPILOTDECK_DESKTOP_DOWNLOAD_MIRROR=china node "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```For fully offline installs, point to a directory containing the matching `chrome-*.zip` archive:```bashPILOTDECK_DESKTOP_PLAYWRIGHT_ARCHIVE_DIR="/path/to/playwright-archives" node "$PILOTDECK_RUNTIME_ROOT/dist/src/extension/plugins/builtin/browser-use/scripts/install-browser.mjs"```## After InstallRetry the browser-use request after the install succeeds. If the current MCP session still reports the old missing-browser error, tell the user to send the same request once more so PilotDeck can start a fresh browser-use session.

Frequently asked questions