← debugai.io

Changelog

Every release, documented.

v2.3.0June 10, 2026

Native VS Code theme, smarter fixes, debug history

Results panel now matches your VS Code theme

The DebugAI panel uses VS Code's own theme colors, fonts, and codicons instead of a hardcoded dark design. Light themes, high-contrast modes, and custom themes all render natively.

Smarter, safer fixes from the engine

Fixes now target exact line ranges so applied patches land precisely where they should. Confidence scores are honestly calibrated — 90+ means the bug was verified in your actual code. When a large file is only partially analyzed, the engine automatically runs a second pass with the full content before answering.

Debug history on your dashboard

A new History tab on the dashboard lists every debug session: the error, language, framework, model used, confidence, whether the fix was applied, and how long the analysis took. Free plan shows the last 7 days; paid plans keep everything.

Terminal capture without touching your clipboard

Analyze Terminal Error now reads command output and exit codes directly through VS Code shell integration. The old clipboard method only remains as a fallback for shells without integration support.

Webview security and telemetry compliance

The results panel runs under a strict Content-Security-Policy with per-render script nonces. The extension now fully respects VS Code's global telemetry setting, including turning it off mid-session.

Model upgrade across all tiers

Analysis runs on Claude Haiku 4.5 across the board, with Claude Sonnet 4.6 handling complex cross-file errors on paid tiers.

v2.2.0June 1, 2026

MCP server — use DebugAI from any AI agent

DebugAI is now an MCP server

The extension exposes a debug_error tool over the Model Context Protocol. Claude Code, Cursor agent mode, and any MCP-aware agent can call DebugAI directly and get root cause plus ranked fixes across your codebase. Auto-registers in VS Code 1.101+ and uses your existing API key.

Agent-aware error handling

Quota and rate-limit responses now tell the calling agent whether retrying makes sense, so agents stop hammering the API once you hit your cap.

v2.1.0April 30, 2026

One-click VS Code connection

Connect VS Code with one click, no copy-paste

Your dashboard now has a "Connect VS Code" button in the Setup and Settings tabs. Click it: VS Code opens, your key is stored in encrypted SecretStorage, and the connection is verified automatically. No command palette, no pasting, no manual steps.

Secure URI auth handler in the extension

The extension registers a vscode://debugai.debugai/auth handler. Keys are validated for correct format and length, stored encrypted, and confirmed against the API before marking as connected.

Safe override when a key already exists

If you already have a key configured and click Connect VS Code from a different account, VS Code shows a confirmation dialog before replacing anything.

Manual key entry still works as fallback

Ctrl+Shift+P → "DebugAI: Set API Key" remains fully functional. If the URI flow does not work (VS Code not installed, browser policy), the copy method is shown immediately below the button.

v2.0.9April 30, 2026

Onboarding accuracy and demo conversion fix

Walkthrough no longer interrupts users who already have a key

The Getting Started walkthrough now only opens for new users without an API key. Existing users upgrading to a new version will no longer see the onboarding flow.

Step 1 walkthrough rewritten, no more false "indexing" message

The first walkthrough step previously claimed your codebase was being indexed before you had set a key. It now correctly explains the sign-in flow and what happens after your key is connected.

Demo panel now prompts you to get a key

After viewing the demo analysis, a "Debug your own code → Get free key at debugai.io" button appears so you can act on what you just saw without hunting for a sign-up link.

Status bar tooltip updated to Ctrl+Shift+P

Tooltip now reads "Ctrl+Shift+P → DebugAI: Analyze Error" across all status bar states, matching the actual command palette workflow.

Sign-up nudge delay extended to 90 seconds

The follow-up prompt after clicking "Get Free Key →" now waits 90 seconds instead of 30, giving you time to complete sign-up before being asked to paste your key.

v2.0.7April 24, 2026

Email, webhook, and onboarding fixes

"See Demo →" in install notification

New users can now try a live demo instantly from the install notification, no API key needed.

Follow-up prompt after sign-up

30 seconds after clicking "Get Free Key →", DebugAI reminds you to paste your key into VS Code.

Fixed Clerk webhook, welcome emails now send

The Next.js middleware was intercepting /api/webhooks/clerk before the route handler. Excluded from matcher, so user.created events now reach the handler and trigger Loops welcome email.

v2.0.6April 24, 2026

Onboarding fixes and signup funnel

Install notification now links to sign-up

New users see "Get Free Key →" which opens the dashboard directly. No more dead-end prompt asking for a key you don't have yet.

Status bar guides new users

When no API key is set, the status bar shows "Get Free Key" and opens the dashboard on click.

Walkthrough re-shows on each version update

The Getting Started walkthrough now re-opens with every extension update so existing users see new features.

Fixed broken logo and dashboard links on setup page

The DebugAI logo and "Open Dashboard" button on debugai.io/start were broken. Both now navigate correctly.

Fixed keybinding conflict with VS Code debugger

The Ctrl+Shift+D shortcut conflicted with VS Code's built-in Run and Debug view. Removed: use Ctrl+Shift+P → DebugAI commands instead.

v2.0.2April 13, 2026

Faster and more accurate debugging

Smarter error routing

Simple errors like NameError and SyntaxError resolve in under 2 seconds. Complex cross-file errors get deeper analysis automatically.

Better root cause detection

Files mentioned in your stack trace are always analyzed, even when they are not semantically similar to the error message. Config files, session managers, and decorators are now found reliably.

Git-aware debugging

Recent file changes are included with every debug request. When a regression causes a bug, DebugAI surfaces it immediately.

Reliable during outages

Automatic retry with fallback means you get results even when the primary AI service has issues.

Guided first-run experience

A new walkthrough shows you how to use DebugAI before your first error.

Demo command

Try DebugAI without needing an error ready.