open source · Chrome · localhost + production

Let your coding agent
see the browser.

Beecork Skeleton hands your app's real console errors and failed network requests to your agent, on demand — localhost or production, in your logged-in session. Stop copy-pasting stack traces.

Download for Chrome

chrome://extensions
ExtensionsDeveloper mode
Load unpackedPack extensionUpdate
Beecork Skeleton0.0.2 · just added
On ●
Beecork Skeleton
Connected ✓ · capture ON
localhost:3000✓ auto
Pair this site
~/my-app $ beecork › the signup is broken ◉ read_dev_signals({ kind: "network" }) [network] POST /api/signup → 500 (2s ago) [pageError] TypeError: cannot read 'id' of undefined ◉ Found it — signup reads user.id before the user exists. Fixing src/api/signup.ts…
Developer mode → Load unpacked → pick the extension folder.
1 · Install
2 · Pair a site
3 · Debug with beecork
Install · about 2 minutes

No store needed.

1

Download & unzip

Grab the latest zip from GitHub Releases and unzip it.

2

Load in Chrome

Open chrome://extensions → Developer mode → Load unpacked → the extension folder.

3

Connect & pair

Start beecork's bridge, click the icon (it auto-connects), enable capture, and Pair this site.

Chrome extensions install via “Load unpacked,” not a double-click installer — the standard developer flow. Full guide in the README.

Why it's safe

Powerful, and private by design.

You hold the fence

Only sites you approve are ever watched — nothing else you browse is touched. The agent can look inside the fence; it can't move it.

Secrets never leave the tab

Tokens, API keys, passwords, and Authorization values are stripped in the browser before any signal is captured.

Local only

Signals go to an inbox on your own machine (127.0.0.1). No servers, no analytics, no account.

Always visible

Chrome shows its own “debugging this browser” banner whenever capture is on, so you always know.

Localhost and production

It rides your real, logged-in tab — so your agent can debug a prod issue in your actual session, not just localhost.

On demand, not a firehose

Your agent pulls a distilled slice with read_dev_signals only when it's debugging — never a constant stream.