What does the Fixcue widget capture?

A user message plus an optional element pick (CSS selector and component stack), the last 60 seconds of console errors and warnings, failed or 4xx/5xx network requests, an optional viewport screenshot, viewport size, and user agent.

How does the coding agent get reports?

Fixcue exposes an MCP server with three tools: list_open, get_bundle, and update_status. Cursor, Claude Code, or any MCP client can pull the repro bundle and write back progress.

How much does Fixcue cost?

Free: one project, 50 items per calendar month. Pro: $19/month or $190/year — up to 3 projects with fair-use ingest and 90-day screenshot retention.

MCP-native · built for coding agents

Bug reports your agent can fix.

One line of JavaScript turns “the button is broken” into a complete repro bundle — selector, console errors, failed requests, screenshot — triaged in seconds and pulled straight into your coding agent over MCP.

Get started free See how it works

index.html — one line, done

<!-- add once, forget it -->
<script src="https://fixcue.app/widget.js" defer
  data-token="fc_pub_…" data-origin="https://fixcue.app"></script>

# user clicks → picks the broken element → done
# your agent reads the bundle — selector, console, network, shot

◆ Cursor◆ Claude Code◆ Windsurf◆ Codex◆ Copilot◆ Zed◆ Cline◆ Aider◆ Cursor◆ Claude Code◆ Windsurf◆ Codex◆ Copilot◆ Zed◆ Cline◆ Aider

How it works

Three steps. No back-and-forth.

The reporter describes the symptom once. The bundle carries everything your agent needs to reproduce it.

Embed the widget

A <10KB gzipped script adds a quiet feedback button to your site. No popup until a user clicks it.

Users report with context

They point at the broken element. We attach its selector, component stack, console errors, failed requests, and a screenshot.

Your agent fixes it

Reports are triaged to fixable / needs_decision / spam in under 8 seconds, then your agent pulls the bundle over MCP and writes the status back.

Features

Built for the agent workflow

Every item is a self-contained repro bundle — not a chat thread.

Element-level repro

CSS selector, React/Vue component stack, click position, and the element's text — the “where” without a screenshot thread.

#pay-btn<CheckoutForm>412, 308

Console & network evidence

Last 60s of errors and warnings, plus failed or 4xx/5xx requests — with query-string secrets stripped before storage.

console.error ×2POST /api/pay → 500

Fast triage

Rule checks and an LLM pass classify every report in under 8 seconds.

fixableneeds_decisionspam

Three MCP tools, that's it

list_open · get_bundle · update_status. Agents pick work up and report back.

Abuse-proof ingest

Origin allowlist, per-IP rate limits, and a free-tier quota — your public endpoint can't become a spam sink.

Private by default

Screenshots live in object storage behind 15-minute signed URLs. Tokens, cookies, and auth headers never leave the user's browser in the payload.

Reporter updates

Users who leave an email get notified when their report is resolved — you write nothing.

<10 KB

widget, gzipped

<8 s

report → triaged

MCP tools, whole API

Pricing

Start free. Upgrade when the reports keep coming.

Every plan includes MCP access and the widget.

Free

1 project
50 items / calendar month
7-day screenshot retention
MCP access included

Start free

Let your agent close the loop.

Users report. Your agent fixes. Free tier, no card.

Get started free