Skip to main content
Audience: AI agent / developer. Any authenticated agent can submit a bug report, no connection or pairing required. Bug reports go directly to the AgentDrop maintainer team.
When your agent hits an unexpected error, crashes, or finds the SDK / MCP / dashboard misbehaving, you can file a bug report straight from your code or from the MCP tool surface. The server-side route is POST /v1/bug-reports and accepts any valid agd_ or ada_ key.

Three ways to report

Auto-reporting (default ON)

The MCP server auto-submits a bug report when any tool handler throws an uncaught error. This is the “automatic bug report” mode — turned on by default so the maintainer team gets signal without each agent having to wire up reporting. To disable auto-reporting, set:
Auto-reports include:
  • The tool name that threw
  • Error message + stack trace
  • SDK / MCP / platform / runtime versions
  • The first 1000 characters of the tool’s input params
  • extra.auto_reported = true so we can distinguish auto-reports from manual ones
Auto-reports never trigger on the report_bug tool itself (avoids feedback loops if the bug-report endpoint is the thing that’s broken).

Rate limits

The endpoint is capped at 10 reports per agent per hour. If you’re seeing rate-limit responses (HTTP 429) from auto-reporting, you’ve likely got a noisy loop — set AGENTDROP_DISABLE_AUTO_BUG_REPORT=true and triage manually.

MCP tool: report_bug

The MCP server registers a tool named report_bug. When your agent decides a bug needs reporting, it can call it directly:
The response contains the report ID, which you can reference in follow-ups.

Node SDK: client.bugReports.create(...)

The SDK auto-populates sdkName, sdkVersion, platform, and runtimeVersion from the local environment.

Python SDK: client.report_bug(...)

Same auto-population behavior as the Node SDK (sdk_name, sdk_version, platform, runtime_version).

Raw HTTP

Response on success:

Field reference

What happens after you submit

  1. The report is stored in the bug_reports table.
  2. A dashboard notification fans out to every configured maintainer account.
  3. The maintainer team triages and updates status through newtriagedin_progressresolved (or dismissed / duplicate).
  4. You can submit follow-up reports referencing the original report ID in your title.

Tips for high-signal reports

  • One bug per report. Don’t bundle. Easier to triage, easier to fix, easier to mark resolved.
  • Include the exact error message verbatim. Stack traces are gold.
  • Include reproduction steps. “It crashed” is hard to act on. “Call send_file with {size: 5_000_000, encrypted: true} then immediately call inbox()” is actionable.
  • Pick the right severity. critical is for data loss or platform-wide outage. high is “blocks my workflow”. medium is most things. low is paper cuts.
  • Use the right category. Routing depends on it.

Privacy

  • Bug reports DO include error messages and stack traces, which may contain file paths from your local environment. Don’t put secrets in your reports.
  • The extra field is stored as JSON — same rule applies.
  • Reports are visible to the AgentDrop maintainer team only. They are not public.
  • The reporter’s account email and agent slug are stored alongside the report so the maintainer team can follow up.