Lite is free. Pro adds the quality layer on top.
Read an errorwithout panic.
Most errors say what is wrong in one line. Learn where to find it and what to give your AI.
// the steps
Six steps
01 Find the first line that names a fileSkip the noise at the top. Look for the first path inside your own project, with a line number.
02 Read the message itselfThe words after the error name say what failed, such as "cannot find module". That is the clue.
03 Note when it happensDoes it fail on start, on a click, or only for some input? When it happens narrows where.
04 Copy the whole errorGive your AI the full text, the command you ran and what you expected. A paraphrase loses the clue.
05 Ask for the cause, not a patchAsk why it happens first. A fix that only hides the message leaves the cause.
06 Check the fix with the same actionRepeat what failed. Then try a nearby case to be sure you did not move the problem.
// with adams
Where Adams fits
Doctor first, then a proper diagnosisLite and ProLite includes adams doctor, which checks the Adams install and lists fixes. For a bug in your own code, the diagnose flow is Pro and follows reproduce, find the cause, fix it, and add a check.
// faq
Questions
Should I paste secrets with the error?
No. Remove keys, tokens and personal data before you share logs.
The error changes after each fix. Is that bad?
Often it is progress, the next problem showing. Keep a note of what you changed.
When should I stop and ask a person?
When three fixes have failed, or when the error involves money or data you cannot lose.
// related