v1.0 — BugDump is live

v1.0.0New featureDenis PovarovAugust 20th, 2026

One script tag. Every bug report your users send now arrives with the screenshot, the console, the network log, and the session replay already attached.

This is the first public release of BugDump.

A single line of HTML puts a floating report button on your site:

<script src="https://bugdump.com/sdk/latest.js" data-api-key="your-api-key"></script>

It renders inside a Shadow DOM, so your styles never leak in and its styles never leak out.

Capture

Screenshots via getDisplayMedia for pixel-perfect fidelity, with automatic fallback to DOM rendering when a user denies the permission prompt
Annotation tools — arrow, rectangle, freehand, text, and a blur tool for redacting anything sensitive before the report ever leaves the browser
Screen recording, again either real screen capture or rrweb-based DOM recording
Voice notes for the reports where typing is the bottleneck
File attachments

Collected automatically, with no user action

Console logs, including everything logged before the widget opened
Network requests, with optional request and response bodies behind captureNetworkBodies
Session replay
User actions and performance timings
Browser, OS, viewport, and page metadata

Triage

Reports land in a project. From there:

A kanban board with columns you define, each mapped to an open or closed state
Tasks with public IDs, comments, and activity history
Reports attach to tasks, so five people reporting the same bug become one task with five pieces of evidence
A public portal at /p/your-project where reporters can follow the task they filed
Filter facets across the report list for narrowing by browser, OS, and more

Reporters can also attach a report to an existing task themselves by its public ID, when you enable allowTaskAttach.

Integrations

Eight destinations: Telegram, Slack, Discord, GitHub Actions, GitHub Issues, Jira, Asana, and Freshdesk.

Telegram and GitHub Issues are available on the free plan. The rest are Pro.

Webhooks

Subscribe to report.created and receive a signed POST the moment a report arrives. Delivery runs through a background queue with retries, so a brief outage on your side does not drop events.

MCP — your AI agent reads your bugs

This is the part we are most pleased with. BugDump ships an MCP server, so Claude Code can read your bug reports as a first-class data source. Seven tools:

Tool	What it does
`get_current_project`	Confirms which project the key is scoped to
`list_tasks`	Finds tasks
`get_task`	Reads one task by public ID
`get_task_activity`	Reads a task's history
`list_reports_for_task`	Lists the evidence on a task
`get_report`	Reads one report — console, network, screenshots
`get_report_telemetry`	Pages through the full telemetry, unabridged

The workflow it enables: paste a task ID into Claude Code, and it pulls the stack trace, the failing request, and the reproduction steps on its own — then fixes the bug.

Each MCP key is permanently bound to one project. There is no way to widen its scope after the fact, which is exactly the property you want in a key you hand to an agent.

API keys

Two scopes: widget for the public-facing SDK, mcp for agent access. They are separate on purpose — the key embedded in your frontend cannot read your reports.

Plans

	Free	Pro — $4.99/mo	Ultra — $9.99/mo
Reports per project	500	10,000	100,000
Storage	1 GB	10 GB	50 GB
Projects	3	20	100
Members per project	3	10	100
Integrations	Telegram, GitHub Issues	All eight	All eight
Webhooks	—	Yes	Yes
Remove branding	—	Yes	Yes

No seat-based pricing, no sales calls. The free tier is a real tier, not a trial.

What's next

Deeper integration coverage, richer replay tooling, and more for the MCP server. If something is missing for your workflow, the feedback board is open.

The widget