Skip to content
Kumak edited this page Nov 22, 2025 · 3 revisions

Browser Debugger CLI

Chrome DevTools Protocol in your terminal. Designed for AI agents and developers who want direct browser control without framework overhead.

Quick Navigation

Page Description
Getting Started Install, first session, basic commands
Commands Complete command reference
For AI Agents Agent-friendly design, exit codes, discovery patterns
Recipes Common workflows and automation patterns
Quick Reference Fast lookup: exit codes, patterns, quick fixes
Architecture How bdg works: daemon, IPC, session lifecycle
Troubleshooting Common issues and solutions

Why bdg?

bdg Puppeteer/Playwright Chrome DevTools MCP
CDP coverage All 644 methods Via CDPSession API 28 curated tools
Self-documenting --list, --search, --describe External docs Fixed descriptions
Discovery Search methods by keyword Know what you need Browse tool list
Interface CLI, immediate Write code first MCP server + client
Token efficient Semantic a11y (70-99% reduction) Raw HTML Verbose responses
Unix philosophy Pipes, jq, composable Programmatic only Protocol-based

5-Minute Quick Start

# Install
npm install -g browser-debugger-cli@alpha

# Start session
bdg example.com

# Explore what's possible
bdg cdp --list                    # 53 CDP domains
bdg cdp --search cookie           # Find methods by keyword

# Run any CDP command
bdg cdp Network.getCookies

# High-level helpers
bdg dom query "button"
bdg dom get 0

# Stop
bdg stop

Key Features

  • Full CDP Access: All 644 protocol methods (53 domains), not a subset
  • Self-Documenting: Discover capabilities via --list, --search, --describe
  • Agent-Friendly: Semantic exit codes, JSON output, predictable behavior
  • Token Efficient: Semantic DOM output reduces tokens by 70-99%
  • Unix Native: Pipes, jq, shell composition

Platform Support

  • macOS and Linux (native)
  • Windows via WSL
  • PowerShell/Git Bash (not yet supported)

Links

Clone this wiki locally