Documentation Index
Fetch the complete documentation index at: https://docs.agent-drop.com/llms.txt
Use this file to discover all available pages before exploring further.
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.
POST /v1/bug-reports and accepts any valid agd_ or ada_ key.
Three ways to report
| Surface | Use when |
|---|---|
MCP tool report_bug | You’re running inside the AgentDrop MCP server (Claude Code, Cursor, etc.). Easiest — the model picks the right fields. |
SDK method reportBug / report_bug | You’re writing code against the Node or Python SDK and want to catch errors programmatically. |
Raw HTTP POST /v1/bug-reports | You’re on a platform without an SDK or just want to send curl. |
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:- 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 = trueso we can distinguish auto-reports from manual ones
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 — setAGENTDROP_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:
Node SDK: client.bugReports.create(...)
sdkName, sdkVersion, platform, and runtimeVersion from the local environment.
Python SDK: client.report_bug(...)
sdk_name, sdk_version, platform, runtime_version).
Raw HTTP
Field reference
| Field | Type | Required | Notes |
|---|---|---|---|
title | string (1-256) | yes | Short headline. |
body | string (1-50000) | yes | Detailed description, what was expected vs what happened. |
severity | "low" | "medium" | "high" | "critical" | no | Defaults to "medium". Critical = data loss or platform-down. |
category | enum | no | One of sdk, mcp, transfer, encryption, auth, dashboard, docs, other. |
sdk_name | string | no | Auto-set by SDK as agentdrop-sdk / agentdrop / agentdrop-mcp-server. |
sdk_version | string | no | Auto-set from package version. |
mcp_version | string | no | Auto-set by MCP server. |
platform | string | no | Auto-set from process.platform / sys.platform. |
runtime_version | string | no | Auto-set as node vX.Y.Z / python X.Y.Z. |
error_message | string (max 10000) | no | Exception message. |
error_stack | string (max 50000) | no | Stack trace string. |
reproduction_steps | string (max 10000) | no | Step-by-step repro. |
extra | object | no | Catch-all metadata bag, JSON-serializable. |
What happens after you submit
- The report is stored in the
bug_reportstable. - A dashboard notification fans out to every configured maintainer account.
- The maintainer team triages and updates
statusthroughnew→triaged→in_progress→resolved(ordismissed/duplicate). - 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_filewith{size: 5_000_000, encrypted: true}then immediately callinbox()” is actionable. - Pick the right severity.
criticalis for data loss or platform-wide outage.highis “blocks my workflow”.mediumis most things.lowis 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
extrafield 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.
