szymdzum/browser-debugger-cli
174 stars · Last commit 2026-10-11
Let Claude Code and other coding agents drive and debug Chrome from the shell. DOM, network, console and raw CDP as short commands, no screenshots and no MCP needed.
README preview
# bdg - Browser Debugger CLI [](https://www.npmjs.com/package/browser-debugger-cli) [](https://github.com/szymdzum/browser-debugger-cli/actions/workflows/ci.yml) [](https://github.com/szymdzum/browser-debugger-cli/actions/workflows/security.yml) [](https://github.com/szymdzum/browser-debugger-cli/pulls) **Give your AI agent a real browser. And the DevTools to go with it.** 📖 **[Wiki](https://github.com/szymdzum/browser-debugger-cli/wiki)**: [Getting Started](https://github.com/szymdzum/browser-debugger-cli/wiki/Getting-Started) · [Commands](https://github.com/szymdzum/browser-debugger-cli/wiki/Commands) · [For AI Agents](https://github.com/szymdzum/browser-debugger-cli/wiki/For-AI-Agents) · [Recipes](https://github.com/szymdzum/browser-debugger-cli/wiki/Recipes) · [Quick Reference](https://github.com/szymdzum/browser-debugger-cli/wiki/Quick-Reference) · [Troubleshooting](https://github.com/szymdzum/browser-debugger-cli/wiki/Troubleshooting) · [CLI reference](docs/CLI_REFERENCE.md) bdg keeps a browser session open in the background and lets you drive it one shell command at a time. Click, fill, navigate, then read what actually happened: requests, console errors, layout and styles. It is built for coding agents like Claude Code, Codex and Gemini CLI, and it's just as handy in your own terminal. Every command is a plain process with compact output, so it pipes into `jq` and costs an agent few tokens. ```bash npm install -g browser-debugger-cli bdg localhost:3000 ``` ## Two ways to use it