diagnostic terminal · v2.0
DebugAI doesn't run your code — it reads it. Give it what the code was supposed to do, the code itself, and what the console shows. It finds the mismatch between the three.
$ describe
Say what the code was supposed to do, in plain language.
$ paste
Drop in the function, component, or file that isn't behaving — any language.
$ console
Add the error if there is one. No error at all works too.
$ diagnose
Get the bug, why it happens, and a fix you can copy straight into your file.
A bug is just a disagreement between three things: what you meant, what you wrote, and what the console says happened. DebugAI's whole job is finding which edge broke. Toggle the code below and watch the triangle react.
var i breaks the loop
It's one of the most common JavaScript bugs there is. Scrub the
slider to watch var share one binding across every iteration, while
let gives each one its own.
for (let i = 0; i < 3; i++) {
setTimeout(() => console.log(i), 100);
}
var i is function-scoped, so every click handler shares the same
i — by the time a click happens, the loop has already finished.
1for (let i = 0; i < items.length; i++) {2 items[i].addEventListener("click", ...);3}
res.json() returns a Promise. Without await, user
is the Promise itself, so user.name is undefined.
1const res = await fetch(url);2const user = await res.json();3nameEl.textContent = user.name;Three real bugs, no hints beyond the console. Click the line you think is wrong before reading the fix — most people get one of these three wrong.
$ intent
Define saveData() before calling it.
1function saveData() {2 ...3}