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.