How to debug an AI-built app
A repeatable method: reproduce it, read the real error, find the layer, change one thing, verify. Written for apps whose code you did not type.
Symptom-first guides: what the error means, what caused it, how to check, and how to know it is really fixed.
A repeatable method: reproduce it, read the real error, find the layer, change one thing, verify. Written for apps whose code you did not type.
A symptom-to-cause index. Start from what you can see — a blank page, an empty list, a failed login, a dead deploy — and follow it to the layer responsible.
A 401 means the server could not identify you. The causes, how to tell which one you have, and how to confirm the fix.
The differences between your machine and a deployment — configuration, case sensitivity, build strictness, real users — and how to find which one bit you.
Empty lists, permission errors and silent failures between the browser and a hosted database — and how to tell which of the three you have.
The variable is set and the code still reads undefined. The six reasons that happens, in the order worth checking them.
How keys end up visible in a bundle or a repository, how to confirm it, what to do in the first ten minutes, and how to stop it recurring.
Your change is committed and the live site is unchanged. Branch, build, cache or domain — how to find out which, in four checks.
Rate limits, token limits, concurrency limits and accidental loops — how to tell which one you hit and how to stop hitting it.
Looking for something else? Browse every topic.