Plans and limits
What each plan includes, what counts as a debug, when counters reset, and every size, rate and time limit DebugAI applies.
Prices change on the pricing page first. If this page and debugai.io/pricing ever disagree, the pricing page is right.
Plans
| Free | Pro | Team | |
|---|---|---|---|
| Price | $0 | $12 a month, or $120 a year | $18 per seat a month, or $180 per seat a year. Minimum 3 seats |
| Debugs | 10 a day | 1,000 a month included | 5,000 a month, pooled across seats |
| At the limit | New debugs stop until the reset | You are told, and not stopped | You are told, and not stopped |
| Proactive Scans | 3 a day, 3 files each | 22 a day, 10 files each | 52 a day, 10 files each |
| Models | Haiku | Haiku, and Sonnet on hard errors | Haiku, and Sonnet on hard errors |
The extension, the MCP server and the ChatGPT and Codex plugin all draw on the same account and the same counter.
- Pro trial. 14 days of Pro with no card. It never starts on its own: start it on the upgrade page with Try Pro free for 14 days. When it ends without a subscription, the account is on Free again.
- Team. Self-serve Team checkout is not live yet. Email support@debugai.io and the account is set up by hand.
- Founding rate. Accounts created before the founding cutoff can claim Pro at $9 a month for life. The dates are on the pricing page.
What counts as a debug
One debug is one error you send and get an answer for, from any surface. These do not count:
- A request DebugAI turns away because it is not an error, such as a terminal prompt or a block of source code. The answer says
This attempt was not counted against your limit. - A request that fails on DebugAI's side. Its slot is handed back.
lookup_errorand the Claude Code hook. Both read memory with no model call.- DebugAI: Try Demo Analysis, which makes no request at all.
- Proactive Scans, which have their own daily count.
When counters reset
| Counter | Resets |
|---|---|
| Free daily debugs | Every day at 00:00 UTC |
| Pro and Team monthly debugs | On the 1st of each month at 00:00 UTC |
| Proactive Scans | Every day at 00:00 UTC |
At the limit
On Free, the 11th debug of the day is refused until 00:00 UTC. The extension says Daily limit reached (10 a day). It resets at midnight UTC. An agent gets the quota_exceeded error, which tells it not to retry. When two or fewer debugs are left, the extension warns you after a debug.
On Pro and Team, 1,000 and 5,000 are soft caps. Past them you keep getting answers, and the extension tells you once a month, with a line on the dashboard. A separate ceiling, well above anything a person types, stops runaway scripts. If an account ever reaches it, debugs are refused until the 1st with Monthly usage ceiling reached. Contact support if this is legitimate. Write to support@debugai.io if that happens to you.
Proactive Scans
| Plan | Scans a day | Files per scan |
|---|---|---|
| Free | 3 | 3 |
| Beta (invited accounts) | 5 | 10 |
| Pro | 22 | 10 |
| Team | 52 | 10 |
A project's first scan may read up to 18 files, and stops after 3 findings. Over the daily count the extension shows DebugAI: Daily scan limit reached with an Upgrade button. A scan request times out after 120 seconds. More in Proactive Scan.
Sizes
| What | Limit |
|---|---|
| Error text | 3,000 characters. The extension and the MCP servers cut longer text to fit, keeping its start and end. |
| Code sent with a debug | 50,000 characters. The extension sends up to 30 lines either side of your cursor, fitted to that. |
| Files the npm MCP server reads for one debug | 3 files, none over 2 MB, 50,000 characters in all |
| Code snippet through the ChatGPT and Codex plugin | Its first 20,000 characters |
Report notes (newError, actualFix, finalFix) | 4,000 characters each from the npm server, 20,000 through the plugin |
| One file in the index | 50 KB. A longer file is cut there. |
| One indexing run | Up to 500 files sent, chosen from up to 4,000 that match |
| Files kept per project on Free | 200. Pro and Team have no file cap. |
Rate limits
These stop floods, not people.
| What | Limit | Counted per |
|---|---|---|
| Any request to the API | 2,000 per 15 minutes | Network address |
| Indexing requests | 600 per 15 minutes | Account |
Memory lookups (lookup_error, the hook) | 300 per 15 minutes | Account |
| Starting a sign-in code | 30 per 15 minutes | Network address |
| Checking whether a sign-in code was confirmed | 90 a minute | Network address |
A burst over a limit gets a wait time back: Too many requests in a short window. Wait about N seconds. in the extension, and rate_limited with the seconds for an agent. No plan raises these limits.
A sign-in code lives 10 minutes, and the extension and the CLI check it every 5 seconds.
Timeouts
| Where | Waits up to |
|---|---|
| The extension, for one debug | 110 seconds |
| The API, for the engine's answer | 90 seconds |
The npm MCP server, debug_error | 150 seconds, or DEBUGAI_TIMEOUT_MS |
The npm MCP server, lookup_error and report_outcome | 8 and 15 seconds |
| The ChatGPT and Codex plugin, for the engine | 50 seconds |
| The extension, for a Proactive Scan | 120 seconds |
| The Claude Code hook | 5 seconds for its input, 8 for the lookup |
If your agent's client has its own tool timeout, set it above the debug_error wait.
Which plan you are on
The dashboard's Settings tab shows your plan, its limit and when the counter resets. The status bar shows what is left: DebugAI (9 left) on a daily plan, DebugAI (120/1000) on a monthly one. npx -y @debugai/mcp status prints the plan for the key your agent uses.
A paused Pro or Team subscription counts as Free until it resumes.
Related
- Answers and limits: every limit message and what to do about it.
- Index your project
- MCP tools