Use this skill when a task needs browser automation through PilotDeck's built-in browser-use plugin, especially for local Web UI smoke tests, screenshots, navigation, clicking, typing, and DOM inspection.

Availability

PilotDeck ships the browser-use plugin, which runs @playwright/mcp with Chromium. The plugin needs Chrome for Testing to be installed on the machine before browser automation can launch reliably.

Check whether the browser is already installed:

if ls "$HOME/Library/Caches/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1 || \
   ls "$HOME/.cache/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1; then
  echo "Chrome for Testing is already installed; no reinstall needed."
else
  echo "Chrome for Testing is not installed yet."
fi

The one-line installer uses the same check. If Chrome for Testing is already present, it prints Chrome for Testing already installed and does not download it again.

Install it from a PilotDeck source checkout or installed app directory:

cd /path/to/PilotDeck
corepack pnpm install --frozen-lockfile
corepack pnpm run install:browser

For an installed one-line setup, use the app directory shown by pilotdeck status:

pilotdeck status
cd ~/.pilotdeck/app
corepack pnpm run install:browser

To let the one-line installer install it during setup, opt in explicitly:

PILOTDECK_SKIP_BROWSER_INSTALL=0 bash install.sh

Repeated installs are safe: check first, skip when present, install only when missing.

If the download is slow or blocked, configure your network proxy first and rerun the install command. Browser automation is optional; PilotDeck core chat, files, skills, and settings work without it.

Usage Notes

Prefer browser-use for interactive browser tasks instead of trying to script raw HTTP requests.
For local PilotDeck checks, open the URL shown by pilotdeck status, usually http://localhost:3001.
If no model provider is configured, a clean PilotDeck instance should land on onboarding rather than settings or chat.
Keep browser tasks small and observable: navigate, wait for a visible heading, inspect relevant text, then report evidence.
Do not store API keys, session cookies, or private credentials in screenshots or logs.

Common Checks

Open http://localhost:3001
Verify the page shows LLM Provider Setup when no real provider config exists
Open Settings and verify provider/API key controls are visible
Take a screenshot only when visual evidence is useful

Más de este repositorio

mismo repositorio

powershell

OpenBMB/PilotDeck

Run safe PowerShell commands on Windows, translate Bash snippets, and troubleshoot native Windows setup.

2026-07-083.8k

meeting-recorder-assistant

OpenBMB/PilotDeck

Intelligent meeting recording and transcription assistant with automated minutes generation, action item extraction, and sentiment analysis. Supports audio transcription, speaker diarization, meeting summarization, and task extraction. Use when users need to record meetings, transcribe audio, generate meeting minutes, extract action items, or analyze meeting content.

2026-06-093.8k

1password

OpenBMB/PilotDeck

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

2026-06-093.8k

apple-notes

OpenBMB/PilotDeck

Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.

2026-06-093.8k

apple-reminders

OpenBMB/PilotDeck

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

2026-06-093.8k

bear-notes

OpenBMB/PilotDeck

Create, search, and manage Bear notes via grizzly CLI.

2026-06-093.8k

browser-use

Availability

PilotDeck ships the browser-use plugin, which runs @playwright/mcp with Chromium. The plugin needs Chrome for Testing to be installed on the machine before browser automation can launch reliably.

Check whether the browser is already installed:

if ls "$HOME/Library/Caches/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1 || \ ls "$HOME/.cache/ms-playwright"/mcp-chrome-for-testing-* >/dev/null 2>&1; then echo "Chrome for Testing is already installed; no reinstall needed." else echo "Chrome for Testing is not installed yet." fi

The one-line installer uses the same check. If Chrome for Testing is already present, it prints Chrome for Testing already installed and does not download it again.

Install it from a PilotDeck source checkout or installed app directory:

cd /path/to/PilotDeck corepack pnpm install --frozen-lockfile corepack pnpm run install:browser

For an installed one-line setup, use the app directory shown by pilotdeck status:

pilotdeck status cd ~/.pilotdeck/app corepack pnpm run install:browser

To let the one-line installer install it during setup, opt in explicitly:

PILOTDECK_SKIP_BROWSER_INSTALL=0 bash install.sh

Repeated installs are safe: check first, skip when present, install only when missing.

If the download is slow or blocked, configure your network proxy first and rerun the install command. Browser automation is optional; PilotDeck core chat, files, skills, and settings work without it.

Usage Notes

Prefer browser-use for interactive browser tasks instead of trying to script raw HTTP requests.

For local PilotDeck checks, open the URL shown by pilotdeck status, usually http://localhost:3001.

If no model provider is configured, a clean PilotDeck instance should land on onboarding rather than settings or chat.

Keep browser tasks small and observable: navigate, wait for a visible heading, inspect relevant text, then report evidence.

Do not store API keys, session cookies, or private credentials in screenshots or logs.

Common Checks

Open http://localhost:3001 Verify the page shows LLM Provider Setup when no real provider config exists Open Settings and verify provider/API key controls are visible Take a screenshot only when visual evidence is useful