Read a result

The panel answers two things: what broke, and what to change. Every fix also says how much of it was checked, so you can tell a tested answer from a confident guess.

The parts of the panelCopy Anchor Link

The answer opens in a DebugAI tab beside your code, headed DebugAI Results.

• Root Cause is the explanation, in plain language.
• A row of badges says where the answer came from (see Badges).
• Ranked Fixes lists up to three fixes, the most likely first.
• Was this helpful? sends DebugAI your verdict (see Tell DebugAI how it went).
• The last line counts what your plan has left: 9 AI debugs remaining today, or on a monthly plan 120 of 1000 debugs used this month.
• Session History, on the left, lists your recent analyses.

Each fixCopy Anchor Link

A fix card shows:

• its rank and title;
• where it applies, as plain text such as cart.py:11 (not a link), and in settings.py when the fix belongs in a different file from the one in the error;
• a confidence figure with a bar: green at 80% and above, amber from 60%, red below 60%;
• one of three verification labels;
• why this fix, then the code;
• Preview & Apply Fix and Copy. See Apply and undo a fix.

No fixes available. means the answer came back with no fix to offer.

The three labelsCopy Anchor Link

Hover a label to see the reason DebugAI gives for it.

A high percentage on a Not verified fix is the model's opinion of itself. Read the diff before you apply it. More in Verification.

BadgesCopy Anchor Link

The first badge is about this error's history in your project, when it has one:

Then, when they apply:

• Cached: the answer came from DebugAI's store of recent answers to the same request.
• 12 files (or another number): the answer drew on that many files from your project index. No badge means no indexed file was used.
• high confidence, medium confidence or low confidence: the analysis's overall confidence.
• A framework name, such as fastapi or nextjs, when one was detected.
• Fast or Full: which model answered. Fast means a Haiku model. Full means any other: Sonnet, which Pro and Team get on hard errors, or the fallback model DebugAI uses when Claude is unavailable.
• The name of a known error pattern, when the error matched one.

How memory works, and how a fix earns "verified": Error memory.

Session HistoryCopy Anchor Link

The last 20 analyses stay in the panel's sidebar, newest first, and survive a restart. Click one to open it again. The footer shows your extension version.

Tell DebugAI how it wentCopy Anchor Link

Thumbs up records the answer as helpful. Thumbs down asks What went wrong? (helps us improve) and offers Wrong fix, Wrong file, Off-target error, Too generic and Other. Other opens the Feedback tab on your dashboard, where you can say more.

Applying a fix records it as helpful by itself, and the thumbs lock for that answer. Copying a fix is recorded too.

When the analysis failsCopy Anchor Link

The reason comes as a notification. If a results panel is already open, a card with the same sentence takes the place of the old answer. Its second button is always Analyze error from terminal.

Full texts and fixes for each: Answers and limits.

Insufficient contextCopy Anchor Link

Sometimes the only fix is titled Insufficient context for specific fix, at 20%. DebugAI could not see enough code to name a cause, and the description says which of four things went wrong:

DebugAI saw the error text but had no project attached, so there was nothing to read your code from. Open your project folder in VS Code, run 'DebugAI: Index Entire Workspace', then try again.

No folder is open. Open your project folder, index it, and run the debug again.

DebugAI read the stack trace and found <files>, but none of it is in your project index yet, so it could not see the code. Run 'DebugAI: Index Entire Workspace' and try again. Indexing runs once and covers every later error in this project.

The files are real but not indexed yet. Index your project and run it again.

The error names no file, so DebugAI had nothing to look up. Paste the full stack trace rather than the last line. If this error genuinely carries no frames, run 'DebugAI: Index Entire Workspace' so DebugAI can search your project for it instead.

You sent the last line of an error. Send the whole trace. When an editor file was sent along and it does not look like the source, the same advice reads:

The error names no file, and the open file does not appear to be where it came from. Paste the full stack trace rather than the last line — the frames are what let DebugAI find the source.

DebugAI had your code and still could not narrow this to one fix. That usually means the cause is outside the files the trace names. Try the error again with more of the surrounding output, or open the file you suspect and run 'DebugAI: Analyze Error' there.

The index worked and the answer still was not specific. Send more of the output, or open the file you suspect and analyse from there.

NextCopy Anchor Link

• Apply and undo a fix.
• Verification, for what each label promises.