Documentation

BRYG v0.3.0 · macOS (Apple Silicon & Intel) · Linux and Windows are on the roadmap

Install

curl -fsSL https://bryg.pages.dev/install.sh | sh

The installer downloads the binary to ~/.bryg/bin/bryg, verifies its SHA-256 checksum, then runs a guided setup that:

Non-interactive: curl -fsSL https://bryg.pages.dev/install.sh | sh -s -- --yes --no-ocr. Re-run setup anytime with bryg setup.

Requirements: macOS, Google Chrome (or a Chromium-based browser via BRYG_CHROME), and an MCP client. BRYG launches a dedicated browser profile — it never touches your daily browser.

Command line

CommandWhat it does
brygStart the MCP server (stdio) — this is what your MCP client runs
bryg setup [--yes] [--no-ocr] [--no-path]Guided setup (re-runnable)
bryg activate <key>Activate your license on this machine
bryg deactivateRelease this machine's license seat (move to another machine)
bryg licenseShow local license status
bryg update [--check]Update BRYG to the latest version (verified by checksum)
bryg browser launch [url] | stop | update [--update]Manage the dedicated automation browser

Configuration

Environment variableMeaningDefault
BRYG_CHROMEPath to a Chromium-based browser binaryGoogle Chrome
BRYG_PROFILEBrowser profile directory~/.bryg/chrome-profile
BRYG_HEADLESS=1Run the browser headlessheadful
BRYG_CDP_PORTDebug port; random picks & persists an unpredictable port9222
BRYG_CDP_HOSTDebug host127.0.0.1
BRYG_OCR_LANGTesseract language(s), e.g. eng+jpneng
BRYG_AUTO_UPDATE=1Self-update automatically in the backgroundoff
BRYG_HOMEData directory~/.bryg

~/.bryg/config.json supports {"ocrLang": "...", "autoUpdate": true} — both are also set by bryg setup.

Tools (43)

Tabs, navigation & history

browser_tabs · browser_new_tab · browser_close_tab · browser_activate_tab · browser_navigate · browser_reload · browser_go_back · browser_go_forward · browser_page_info

Perception

browser_snapshot (accessibility tree with stable [ref=N] element handles, filterable) · browser_read (page text / links) · browser_screenshot · browser_ocr (multi-strategy, any tesseract language) · browser_qr (decode QR codes)

Pointer actions (by ref or coordinates, dispatched as trusted input events)

browser_click · browser_click_text (click by visible text) · browser_double_click · browser_right_click · browser_long_press · browser_hover · browser_drag · browser_scroll · browser_scroll_to

Keyboard & forms

browser_type · browser_press_key (combos like Control+Shift+T) · browser_fill · browser_replace (select-all-and-replace; reliable on React controlled inputs) · browser_select_option · browser_focus · browser_upload · browser_login_fill (credentials from a local file — values never enter the AI conversation)

Advanced

browser_evaluate (run JS) · browser_wait · browser_set_viewport · browser_pdf · browser_clipboard_read / browser_clipboard_write (move data across tabs via the OS clipboard, no permission popups)

Network recording

network_start (record everything, keyword-filtered, or failures-only; sensitive headers/fields masked by default — see Security) · network_stop · network_status

XPath generation

xpath_by_text · xpath_at (from coordinates) · xpath_for_ref — short, semantic, verified-unique selectors for your test suites

Updates

BRYG checks a static version file at startup (anonymously, at most once per 24h). When an update is available, your AI assistant relays a short notice in the session — run ~/.bryg/bin/bryg update, then restart your MCP client. Prefer hands-off? Enable auto-update in bryg setup or with BRYG_AUTO_UPDATE=1.

License & billing

Where is my license key?

In your purchase email from Lemon Squeezy. You can always retrieve it from the customer portal link in the same email.

Moving to a new machine

Run bryg deactivate on the old machine (or deactivate the instance in the customer portal), then bryg activate <key> on the new one. One key = one active device.

Cancel / refund / change card

All self-serve in the Lemon Squeezy customer portal (linked in every receipt email). Cancelling during the 3-day trial means you're never charged.

What happens offline?

BRYG validates your subscription at startup and caches the result — you can work offline for up to 72 hours without re-validation.

Uninstall

Remove the MCP registration from your client (e.g. claude mcp remove bryg), then delete ~/.bryg. If setup created a PATH symlink (/opt/homebrew/bin/bryg, /usr/local/bin/bryg or ~/.local/bin/bryg) or an rc-file line marked # added by bryg, remove it too. That's everything.

Changelog

0.3.0 — 2026-07-14

0.2.0 — 2026-07-14

0.1.0 — 2026-07-14