Commands and shortcuts
Every command the VS Code extension adds, where each one appears, and the one default keyboard shortcut.
The extension adds 13 commands. Open the Command Palette (Ctrl Shift P, or Cmd Shift P on a Mac) and type DebugAI to list them all. The same commands run in Cursor, Windsurf and VSCodium.
All commands
| Command | ID | What it does |
|---|---|---|
| DebugAI: Analyze Error | debugai.analyze | Debugs the error you selected, the error on the line under your cursor, or one you paste. |
| DebugAI: Analyze Terminal Error | debugai.analyzeTerminal | Finds the last failing command in the terminal and debugs its error. |
| DebugAI: Sign In | debugai.signIn | Connects the editor to your account with a code you confirm in the browser. |
| DebugAI: Set API Key | debugai.setApiKey | Offers the browser sign-in, or a box to paste a key that starts with dbg_. |
| DebugAI: Clear API Key | debugai.clearApiKey | Removes the stored key from this editor and signs it out. |
| DebugAI: Index Entire Workspace | debugai.indexWorkspace | Indexes the open project now, whatever debugai.autoIndex says. |
| DebugAI: Index Current File | debugai.indexProject | Indexes only the file in the active editor. The ID says project; the command does one file. |
| DebugAI: Check Index Status | debugai.checkIndex | Says whether indexing is running, or how many files this window has indexed. |
| DebugAI: Scan Workspace (Proactive) | debugai.scanWorkspace | Runs a Proactive Scan of the files you changed recently. |
| DebugAI: Debug in Browser | debugai.debugInBrowser | Opens your local dev server in Chrome or Edge and catches errors the terminal never shows. Closed beta, see Debug in Browser. |
| DebugAI: Show Browser Captures | debugai.browserCaptures | Lists the errors caught in the current browser session, to pick one to debug. |
| DebugAI: Try Demo Analysis | debugai.runDemo | Opens a pre-made answer to a sample crash. Needs no key, makes no request and does not count. |
| DebugAI: Open Dashboard | debugai.openDashboard | Opens your dashboard on debugai.io in the browser. |
Where else they appear
| Place | What runs |
|---|---|
| Right-click in the editor | DebugAI: Analyze Error, while the editor has focus |
| Right-click in the terminal | DebugAI: Analyze Terminal Error |
| The DebugAI item in the status bar, signed in | DebugAI: Analyze Error |
| The same item, signed out (it reads DebugAI: Get Free Key) | DebugAI: Open Dashboard |
| Analyze error from terminal, a button in the results panel | DebugAI: Analyze Terminal Error |
| Fix with DebugAI, the quick fix on a DebugAI warning in the Problems panel | DebugAI: Analyze Error |
| DebugAI: watching, the status bar item during a browser session | DebugAI: Show Browser Captures |
The status bar item also counts what is left on your plan, for example DebugAI (9 left) on a daily plan or DebugAI (120/1000) on a monthly one.
Keyboard shortcut
There is one default shortcut.
| Keys | Command | When |
|---|---|---|
| Ctrl Alt D (Windows, Linux) | debugai.analyze | The editor has focus |
| Cmd Alt D (macOS) | debugai.analyze | The editor has focus |
It does nothing while the terminal has focus. From the terminal, right-click and pick DebugAI: Analyze Terminal Error, or give that command a shortcut of its own.
Add your own shortcut
Run Preferences: Open Keyboard Shortcuts (JSON) from the Command Palette and add an entry. The key below is an example; pick any combination your editor does not already use.
[
{
"key": "ctrl+alt+shift+d",
"command": "debugai.analyzeTerminal"
}
]Add "when": "terminalFocus" to the entry if you want the shortcut to work only while the terminal has focus. Any command ID from the table above can be bound the same way.
Not in the palette
The extension also registers debugai.openAnnouncement, which has no title. It is what a click on a pinned product notice in the status bar runs. You do not need to call it.
Related
- Settings: the four
debugai.*settings. - Debug an error: which command to use for which kind of error.