Shipped: AI Error & Stack Trace Explainer.
Most people paste a single error line into a chatbot and lose the causal chain through the call stack. This explains the full trace, auto-detects the language (JS/TS/Python/Java at minimum), and outputs three things: plain-English explanation, likely root cause, and a concrete next debugging step.
Example: TypeError: Cannot read properties of undefined (reading map) thrown inside a React render, 3-line trace through a .then() callback. A generic paraphrase just restates “you’re reading a property of undefined.” This traces it to the actual likely cause — an API response rendered before a loading-state check — and suggests guarding the render or defaulting the array. That’s the difference between explaining an error and helping someone fix it.
