Browser debugging built for Claude Code.

Bespoke, lightweight debugging tool with built-in Claude Code integration. Fast SQL queries, zero cloud, 100% local.

Claude Code skill: ask AI to diagnose logs
CLI tools: bun run check errors
100x faster than browser-tools MCP
~/browser-logger
$ bun run check errors
✓ Recent Errors (last 5 minutes)
❌ [error] Failed to fetch user data
at /dashboard.js:45
timestamp: 2024-10-27T07:30:15.234Z
⚠️ [warn] Slow network request
GET /api/data → 2340ms
timestamp: 2024-10-27T07:30:12.120Z
ℹ️ [info] Database synced
timestamp: 2024-10-27T07:30:08.567Z
$ bun run query -- "SELECT * FROM network_logs WHERE total_time > 1000"

Why Browser Logger, Not browser-tools MCP?

❌ Without Browser Logger

  • browser-tools MCP is slow & steals context tokens
  • Debugging breaks your AI-assisted workflow
  • DevTools and Claude Code work in isolation
  • Generic tools don't fit your needs
  • Logs disappear on reload (no persistence)

✅ Browser Logger

  • Built-in Claude Code skill for instant diagnostics
  • CLI tools: bun run check errors
  • Query logs with SQL (no context overhead)
  • Logs persist for 5 minutes (locally, 100% private)
  • Zero cloud. Bespoke tool. Built for you.

Powerful Features

Everything you need to debug modern web applications effectively

Claude Code Skill

Claude Code Skill

Built-in Claude Code skill for instant log diagnostics. Ask Claude to analyze errors—no context overhead, instant results.

CLI Tools

CLI Tools

bun run check errors - Quick commands for common queries. No context switching, instant results.

Console & Network

Console & Network

Unified logging for console messages, errors, rejections, and network requests. One place for everything.

SQL Queries

SQL Queries

Query logs with SQL. Find exactly what you need in milliseconds. REST API for integration with other tools.

Lightweight

Lightweight

Less than 1ms overhead. 100x faster than browser-tools MCP. No context bloat. Bespoke, not generic.

100% Local

100% Local

Zero cloud. Zero telemetry. All data stays on your machine. Built for privacy and security.

Get Started in 5 Minutes

Zero configuration. Just install, load, and start debugging.

1

Use Claude Code Skill

# Ask Claude Code in your project:
"check browser logs for recent errors"
# Claude runs the built-in skill automatically
2

Or Use CLI Tools

bun run check errors           # See recent errors
bun run check search "timeout" # Search logs
bun run query -- "SELECT * FROM console_logs"
3

Start Backend Server

bun run logger start
# Server listens on http://localhost:3001
4

Load Extension

chrome://extensions → Load unpacked → Select extension/ folder
# Now all logs are captured to SQLite

Privacy-First Design

Your debugging data stays on your machine. Always.

✅ What We Do

  • ✓ Store logs in local SQLite database
  • ✓ Run API on localhost only
  • ✓ Auto-cleanup after 5 minutes
  • ✓ Never touch external services
  • ✓ Open source & auditable

❌ What We Don't Do

  • ✗ Send data to cloud services
  • ✗ Track usage or analytics
  • ✗ Require authentication
  • ✗ Share data with third parties
  • ✗ Sell or monetize your data
100% Local

100% Local

Open Source

Open Source

MIT Licensed

MIT Licensed

Zero Telemetry

Zero Telemetry

Ready to Debug Better?

Browser Logger is free, open source, and ready to use. No sign-up required.

Made by Cory Feign

Part of a suite of developer tools for modern web debugging

Explore more projects →