Stack Trace Triage · for VS Code, Cursor, VSCodium and Windsurf

Select the stack trace. Press one key. Get the root cause from your own code.

It opens the files at the lines of the trace before it answers, so the diagnosis quotes what is on your disk, not a guess of it. No more pasting the error into a chat and then pasting the code, file by file.

A trace copied from the terminal and its diagnosis with the root cause and the fix

Why I built it

Pasting errors into a chat and re-pasting the code is slow

A stack trace already says where to look: the file and the line of every frame. A chat window cannot open those files, so you copy the error, then the code, then the other file, and the answer is still a guess about code it saw in pieces.

Stack Trace Triage does the copying for you. It parses the frames, opens the actual files at the line numbers from the trace, skips the framework’s own code, and sends the source around each frame together with the error.

Ciro Cesar Maciel, who builds and maintains it

How it works

From the error to the fix in one key

1

Select or copy

Select the trace in any editor or log file, or copy it from the terminal.

2

Press one key

Cmd+Alt+T (Ctrl+Alt+T), or "Triage Stack Trace from Clipboard" from the terminal.

3

It reads your code

Each frame is resolved to a file in your workspace; node_modules, site-packages, vendor, dist and build are left out.

4

Read the answer

Root cause, why it fails, the fix as a diff against the lines it read, and what it would need to be sure.

See it in action

From the terminal: copy the error, and the frames become your files

A real run of a small orders service. The trace that went in:

What went in

TypeError: Cannot read properties of undefined (reading 'tier')
    at loyaltyDiscount (src/pricing/discounts.ts:10:54)
    at computeTotals (src/orders/totals.ts:19:5)
    at settle (src/jobs/settle-orders.ts:10:18)

What came out

Root cause: customer.loyalty is undefined for at least one order. The ?? 0 only guards against an unknown tier; it does nothing when loyalty itself is missing, because customer.loyalty.tier throws before the lookup happens.
Why it fails: orders are loaded with JSON.parse and cast to Order[]; TypeScript does no runtime validation, and settle has no try/catch, so one bad record kills the whole batch.
Triage from the clipboard: the frames resolved to files in the workspace

And then

The fix comes as a diff against the lines it read

Not a rewrite of a file it never saw: a change to the exact lines of the frames, so you can read it in seconds and apply it with confidence.

The fix shown as a diff against the lines of the frames

And then

From any editor or log file

Select the error, press the key, and the diagnosis opens as a Markdown document with a rendered preview, next to your code.

A diagnosis with root cause and fix for a selected trace

Everything in it

Built to answer about your code, not about code in general

Grounded in your files

Each frame is resolved against the workspace: absolute path, path relative to a folder, then a search by file name for compiled or file:// paths.

Seven runtimes, plus a fallback

Node/V8, Python, Java/Kotlin/Scala, Go, Rust, Ruby and PHP frames, and a generic path:line pattern for anything else.

Skips the noise

Frames in node_modules, site-packages, .cargo, vendor, dist and build are left out, so the model reads your code.

Editor, log file or terminal

Select and press Cmd+Alt+T, right-click, or triage straight from the clipboard.

A fixed, readable shape

Root cause, why it fails, the fix, and what it would need to see to be sure. Environment errors are called out as such.

In your language

The diagnosis can be written in the language you work in.

Production traces too

When the paths in a trace do not match your machine (a container, a CI runner, compiled output), it finds the file by name.

Your model, or ours

Free: any model on OpenRouter with your own key, pay per token. Pro: the AI included, no account, no key.

Before you choose

How it compares

Stack Trace Triage

Copilot Chat / ChatGPT

Rubberduck

Stack Trace Formatter

Reads the files from the trace automaticallyYesPartial: you attach themNoNo
Diagnosis and fixYesYesYesNo: formatting only
Node, Python, Java, Go, Rust, Ruby, PHPYesYesYesPartial
Any model, pay per tokenYesNo: subscriptionPartial—
Works in Cursor and VSCodium (Open VSX)YesNoYesNo

From each extension’s public listing. Something changed? Tell me at ciromaciel.click/contact.

Free and Pro

Free does everything. Pro skips the AI account.

The free version keeps every feature, with your own OpenRouter key. Pro is for when you would rather not create one more account and paste one more key: the AI comes included.

Free

$0

  • Every runtime, every source: editor, log file, terminal
  • Diagnoses with your own OpenRouter key, any model, pay per token
  • The frame parsing and the file resolution run on your machine
Install free

Pro

  • Diagnoses with no OpenRouter account and no key

  • One license key, any editor; it also unlocks SQLite Editor Pro if you subscribe to both

  • Claude Haiku 5.5, up to 50 AI requests a day

Loading the price…

Questions

Before you install

Try it on the next error you hit.

All 11 extensions