Paste a crash log. Jump straight to the exact broken line. Get an AI explanation of the fix — without leaving VS Code.
No more scrolling through a wall of stack trace text trying to figure out which line is actually yours and which is buried framework noise.
What it does
- Paste any crash log — Node.js, Python, Java, or C#/.NET
- Automatically finds the real lines in your own code, and filters out framework/library noise (
node_modules, JDK internals, Python'ssite-packages, etc.) - Click a frame to jump straight to it — opens the file and lands your cursor on the exact line
- One click for an AI explanation — sends the error plus the real surrounding code to an AI model, and gets back a plain-English root cause and a suggested fix
How to use it
- Click the Stack Trace Explainer icon in the Activity Bar (the left-hand sidebar) — or open the Command Palette (
Ctrl+Shift+P/Cmd+Shift+P) and run "Stack Trace Explainer: Paste a Stack Trace" - Paste your error output into the box
- Click Find lines — clickable rows appear for every frame in your own code
- Click any row to jump straight to that file and line
- Click Explain top error with AI for a root-cause explanation and fix suggestion
Supported languages
| Language | What gets filtered out automatically |
|---|---|
| Node.js | node_modules, Node's internal (node:...) frames |
| Python | site-packages, dist-packages, the standard library |
| Java | JDK internals (java.*, javax.*, jdk.*, sun.*) |
| C# / .NET | Framework frames with no source available |
A couple of honest notes
- The Explain button calls a small backend that talks to an AI model. It's rate-limited to keep it free and available for everyone — if you see a "too many requests" message, just wait a minute and try again.
- For Java specifically: third-party library frames (e.g. Spring, Hibernate) aren't filtered the way
node_modulesorsite-packagesare — Java stack traces don't include enough path information to reliably tell "your code" from "someone else's library" beyond the JDK itself.
Feedback
Found a trace format that doesn't parse right, or a bug? Open an issue on GitHub — real crash logs from real projects are exactly how this gets better.