The AI-enabled browser for development

Run your dev server through dev3000 to capture server logs, browser events, network requests, and screenshots in a unified timeline. Your coding agent gets complete context without you manually copying and pasting.

Get Started

Quick Start

Install dev3000
For the best experience, install tmux first:
```
brew install tmux
```
Then install dev3000:
```
bun install -g dev3000
```
npm and pnpm installs also work.
Start your dev server
Replaces your normal dev command. Starts your dev server & launches a monitored Chrome instance.
```
# Instead of running bun run devd3k # or dev3000# Setting a portd3k -p 5000# Custom scriptd3k -s build-start
```
Use your app normally
Interact with your app in the monitored browser. Every log, request, error & page state is captured automatically.
Ask your coding agent to debug
Your agent sees everything: server output, client-side events & visual state at every step.

Demo

Server Logs

Timestamped server logs

Browser Events

Logs, errors & user interactions

Screenshots

Captured on errors & navigation

Network Requests

Complete HTTP requests & responses

Frequently Asked Questions

Which coding agents work with dev3000?

All of them. dev3000 works with any AI coding assistant that can read a skill file or follow CLI output—including Claude Code, Cursor, Windsurf, Codex, and others. It also works standalone in your terminal without any agent.

Does dev3000 persist browser state between sessions?

Yes. Each project gets a dedicated Chrome profile that preserves login state, cookies, and local storage.

Can I use Arc or another browser instead of Chrome?

Yes! Use the --browser flag with the path to any Chromium-based browser. For Arc: d3k --browser '/Applications/Arc.app/Contents/MacOS/Arc'

Does this only work with Next.js?

No. Works with any framework that runs a dev server—Next.js, Vite, Create React App, Rails, Django, etc. Use --script to specify your package.json dev command or --port to connect to an existing server.

How do I stop dev3000?

Ctrl+C terminates the dev server and browser simultaneously.

Does dev3000 affect my app's performance?

Minimal impact. dev3000 observes browser events passively through Chrome DevTools Protocol. The only overhead is capturing screenshots on errors and navigation, which happens asynchronously.

Where is my data stored?

All data stays local on your machine. Browser profiles are stored in ~/.dev3000/profiles, and captured events are kept in memory during your session. Nothing is sent to external servers.

Can I use dev3000 with my existing dev workflow?

Yes. Replace your normal dev command (bun run dev, npm run dev, etc.) with d3k. Everything else works exactly the same—hot reload, environment variables, custom ports, etc.