Labsco
Labsco/Repos/vercel-labs/dev3000
REPO PACKAGE

vercel-labs dev3000

COMMUNITY
vercel-labs · publisher1,542 repository starsMIT · Freegithub.com/vercel-labs/dev3000
3skills
0ready to use

The core tool starts your project's dev server, opens a browser through the Chrome DevTools Protocol, and captures server logs, browser console messages, network requests, screenshots, and user interactions into one timestamped timeline an AI agent can read. It works with any framework that has a dev server — the README names Next.js, Vite, Django, Rails, and others — and can run alongside an agent in a split-screen tmux session.

Of the three skills, d3k is the general one: it starts or reuses a running d3k session, waits for it to be ready, and hands an agent the combined browser-and-server evidence to debug an issue. analyze-bundle is narrower — it only converts Next.js bundle-analyzer output to NDJSON, so it is useful on Next.js projects specifically. deepsec runs a separate scanner, DeepSec, against a project checkout that d3k has already set up; that is a second tool being orchestrated here, not part of dev3000 itself.

READ THE FULL ANALYSIS

What it costs to start. The d3k and analyze-bundle skills need only the CLI installed locally (bun install -g dev3000, or npm/pnpm) — no account. deepsec is the one skill of the three that needs an account or key of its own, since it calls out to that separate scanning service.

Who this is for. Anyone debugging a running web app with an AI coding agent already in the loop — the pitch is literally telling the agent to fix the app and letting it read the combined log. It is not useful without a project to point it at, and the deepsec skill only makes sense on a project already hosted on Vercel.

1,542Stars on the GitHub repository, at last check.