// setup

Set it up once.

Pick where you debug. Everything below is two or three short steps, and none of them ask you to paste an API key into a web page.

extension · one-click fix apply, proactive scan, codebase indexing

Install the extension in VS Code

One click from the Marketplace, then reload when prompted.

DebugAI on the Marketplace

Or inside VS Code: extensions panel, search DebugAI, install.

Sign in from inside the editor

Press Ctrl+Shift+P and run DebugAI: Sign In. Your browser opens, you confirm a short code, and VS Code stores the key itself. Free account, 10 debugs a day, no card. Nothing to copy.

Prefer the browser first? Sign in on the dashboard and press Connect there instead. Same result, and it is the better route if this machine cannot open a browser from the editor.

Open the dashboard instead

Debug something

Run the command that fails in VS Code's terminal, then right-click inside the terminal and pick DebugAI: Analyze Terminal Error. For an error in a file, select it and press Ctrl+Alt+D. You get the root cause, up to three ranked fixes, and a one-click apply with a native diff you review like a PR.

First debug in this project? Run DebugAI: Index Entire Workspace once from Ctrl+Shift+P, so the answer can read every file and not only the one that crashed.

Nothing to try yet? Your first debug ↗ has a three-file project with a planted bug, where the crash and its cause are in different files. Or run DebugAI: Try Demo Analysis to see a pre-made answer.

Using an AI agent instead of the editor UI? The gives the same engine to Claude Code, Claude Desktop, Zed, Cline and Gemini CLI. @debugai/mcp

// what the free tier is

10 debugs a day, free, no card. That is most Tuesdays covered. Simple errors route to a fast model; the ugly cross-file ones route to a stronger one on paid tiers, and the response tells you which one answered. Analyses run on our servers, so the error text and any snippet you send go there. Privacy policy.

Pricing →Changelog →Support →Status →