Start here

DebugAI finds the root cause of an error by reading your project, not only the line you paste. It answers with up to three ranked fixes, and you review each one as a diff before anything in your files changes.

Pick where you debugCopy Anchor Link

You can use more than one. They sign in to the same account and draw on the same daily limit.

The first five minutesCopy Anchor Link

Every setup is the same four moves:

1. Install the extension, or run one command for your agent.
2. Sign in. Your browser opens, you confirm a short code, and you are connected. Free account, no card, no API key to copy.
3. Index your project. DebugAI reads your source files once, so an answer can point at the file that broke and not just the file that crashed. Skip this and it sees the error and the code around your cursor, not the rest of your project. See Index your project.
4. Debug an error. From the terminal, the editor or your agent. You get a root cause and ranked fixes.

No error to try it on? Your first debug gives you a three-file project with a bug planted in it, where the line that crashes is not the line that is wrong.

What it costsCopy Anchor Link

10 debugs a day on the free plan, with no card. The count resets at 00:00 UTC. A request DebugAI turns away because it is not an error, or one that fails on its side, is not counted. Pro is $12 a month for 1,000 debugs. See Plans and limits.

When something goes wrongCopy Anchor Link

The troubleshooting pages are written by symptom. Their headings are the exact messages DebugAI shows, so you can search for the text on your screen with Ctrl K.

• Sign-in and keys
• Indexing
• Answers and limits
• The MCP server

For your agentCopy Anchor Link

These docs are written for agents too. Add .md to any page address to get it as Markdown, or point your agent at llms.txt for the index and llms-full.txt for everything in one file.