Skip to main content
GSD Browser is a native Rust browser automation CLI that drives Chrome and Chromium through the Chrome DevTools Protocol (CDP). Unlike script-based frameworks, it runs a persistent background daemon that owns the full browser lifecycle — page routing, network hooks, action timeline, and session state — while a thin CLI client sends it commands. AI agents connect through the MCP server mode (gsd-browser mcp), which exposes over 50 discoverable tools, live resources, and executable prompts to any MCP-compatible client.

​
What makes GSD Browser different

GSD Browser is designed for serious, auditable, human-collaborative agentic web work. Several capabilities set it apart from conventional browser automation tools.

Versioned element refs

gsd-browser snapshot scans the page and assigns stable refs like @v1:e1. Refs are version-stamped and stale-safe — old refs from a previous snapshot are automatically rejected when the DOM changes.

Live authenticated viewer

gsd-browser view opens a real-time localhost workbench so humans can watch, annotate, take over control, pause, step through actions, and resume — without interrupting the agent loop.

Session recording & evidence bundles

Record any flow as a rich, redacted evidence bundle. Bundles auto-convert to commit-ready Playwright regression tests via browser_generate_replayable_test.

Semantic intents

browser_act and find_best cover 15 built-in intent patterns — fill email, submit form, accept cookies, paginate, and more — so agents express what to do, not how.

Action cache & self-healing

Successful intent-to-selector mappings persist in a per-session cache. Future runs reuse them automatically, making long-running agent projects progressively more reliable.

Encrypted credential vault

gsd-browser vault-save stores credentials encrypted on disk. browser_vault_login replays them without ever exposing raw secrets in prompts or logs.

Network control

Mock routes, block URLs, export HAR files, and start CDP traces — all in the same tool, with no separate proxy or plugin required.

50+ MCP tools for agents

gsd-browser mcp exposes the entire daemon surface as MCP tools, resources, and executable prompts. Connect Cursor, Claude Desktop, VS Code Copilot, or any MCP client instantly.

​
Architecture overview

The daemon starts automatically the first time you run any browser command. It maintains an open Chrome instance, tracks page targets, buffers console and network logs, manages named sessions, and serves all commands over a local loopback HTTP channel. The CLI and the MCP server both talk to the same daemon — they share identical semantics and reliability guarantees. 
┌─────────────────┐     JSON-RPC      ┌──────────────────────┐
│  gsd-browser    │ ◄────────────────► │   daemon (localhost)  │
│  CLI / MCP      │                   │   browser lifecycle   │
└─────────────────┘                   │   page routing        │
                                       │   session state       │
                                       └──────────────────────┘
                                                │ CDP
                                       ┌────────▼─────────┐
                                       │  Chrome / Chromium │
                                       └──────────────────┘
The daemon starts automatically on the first browser command. You rarely need to manage it manually. Use gsd-browser daemon health to inspect its state without triggering a start.

​
Primary paths

Choose the path that fits your workflow:

Installation

Install via npm, one-line script, pre-built binary, or build from source.

Quickstart

Start the daemon, navigate a page, take a snapshot, and interact with elements in minutes.

MCP Server

Connect any MCP-compatible AI agent to the full GSD Browser surface in one command.