
D3k
If you're coding in Cursor, Codex, or Claude Code and keep losing track of what's breaking in your web app, this gives the AI a unified view. Instead of running npm dev directly, it boots d3k as the runtime so server logs, browser console, network events, and screenshots land in one timeline. The agent gets a stable CDP endpoint to control the same browser it's monitoring, which beats launching separate automation sessions. Includes a fresh-profile workflow for Codex when you need clean state, plus clear rules on when to use agent-browser versus next-browser. Practical if you want your AI to debug with the full picture instead of guessing from partial logs.
- skills.sh installs
- 877
- GitHub stars
- 1.6K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add vercel-labs/dev3000 --skill d3k --agent claude-codeInstalls into .claude/skills of the current project.
Files
d3k
Own the project's dev server and monitored browser through a small background runtime. No global d3k installation is needed. Evidence stays in bounded memory; browser authentication stays in the project Chrome profile.
Use node <skill-directory>/scripts/runtime.mjs as runtime below, from the target project root. In a development checkout the helper runs the source with Bun; installed skills use the JavaScript package through pnpm dlx (Node.js 24+ and pnpm required). Package acquisition runs in an isolated temporary directory so the target app’s pnpm workspace settings do not affect it; runtime commands still run against the target project. To try unreleased source from another project, set D3K_RUNTIME_ROOT to the dev3000 checkout. Do not use a previously published package to test unreleased changes.
Desktop MCP connection
Sponsors
Details
- Repository
- github.com/vercel-labs/dev3000
- Categories
- Backend & APIs, Testing & QA, Git & Pull Requests, Debugging, Automation & Workflows, Cloud & Infrastructure
- First seen
- May 16, 2026