Feedbug is a visual bug reporting tool that creates Linear tickets with full diagnostics and lets AI agents trace bugs to source code via MCP.
What is Feedbug?
Feedbug captures screenshots, console logs, JavaScript errors, failed network requests, and device metadata whenever a user clicks on a bug on your live site. It writes a Linear ticket automatically and provides an MCP server that Claude Code, Cursor, Windsurf, and VS Code can plug into to read the report, locate the offending source file, and propose a patch. The product is delivered as a single script tag — no SDK, no build step — and works with any framework (React, Vue, Angular, Svelte, plain HTML).
Key Features
- Visual bug reporting — Users click exactly where the bug appears on the page; Feedbug captures the screenshot, the clicked element’s CSS selector, component name, attributes, and siblings.
- Auto Linear tickets — Each bug creates a Linear ticket in under two seconds, attributed to the reporting user, with embedded screenshot, pretty-printed diagnostics, and a link to the live pin.
- Full diagnostics — Includes console logs (info, warn, error), JS stack traces with file and line numbers, failed network requests (4xx/5xx) with URL and timing, and device info (OS, browser, screen size, pixel ratio).
- Visual pins — Numbered markers stay pinned to the correct coordinates even after browser resize or mobile viewport changes; resolved bugs disappear automatically.
- MCP server for AI debugging — The MCP server lets AI assistants read the bug report, its diagnostics, and the surrounding HTML context, then trace back to source code and apply a fix — without leaving the editor.
- Session replay — Captures the 30 seconds of user activity before the bug report for additional context.
- Custom data capture — Configure Feedbug to also send cookies, localStorage, or sessionStorage values with each report.
- Environment control — Restrict the script to specific domains; nothing runs in production unless you explicitly allow it.
Who is it for?
- QA teams — Click on any buggy element, drop a comment, and the ticket is created automatically with all the context developers need.
- Developers — Receive Linear tickets with complete diagnostics (console errors, network failures, element selector) so you never hear “can’t reproduce”.
- AI agents — Plug the MCP server into Claude Code, Cursor, or Windsurf to automatically diagnose and patch the bug from the report data.
- Clients and testers — Report issues visually without writing structured bug reports; everything is captured automatically.
What can you do with Feedbug?
- Report a bug in two minutes — Paste one script tag into your HTML, have your team click on the bug, and a Linear ticket lands with a screenshot, console logs, and device info. See how it works
- Automate ticket creation — Feedbug writes a Linear ticket with all diagnostics in under two seconds, attributed to the person who reported it, so no manual triage is needed.
- Debug with AI — The MCP server feeds the bug report to your AI assistant, which reads the source code, diagnoses the root cause, and opens a pull request with the fix.
- Track reported bugs visually – Numbered pins stay on the exact spot across viewport sizes; click any pin to see details, add comments, or update the Linear ticket status.
