reports 
fix.
MC
Browser, device & release
The browser, OS, viewport and deployed release it happened on.
Bugreports your agent canfix.
One script tag captures what actually happened on the page and hands it to your agent, your tracker and your team. Rebase is the layer in between.
Not four log dumps. One causal timeline.
Every report is one ordered timeline: the clicks, console errors and failed requests that led to the bug. Nothing to cross-reference.
Console errors
Uncaught exceptions, rejections and warnings, in order.
Failed requests
Sorted by failure kind, including GraphQL errors inside a 200.
Screenshot
The page at the moment it was flagged, masked fields intact.
The steps that led there
Every click and input, with dead clicks and rage clicks flagged.
The pinned element
Its markup, computed styles and ancestors.
Errors nobody reported
On Pro, errors from real sessions queue for review before anyone files a thing.
Down to the file and line. Sourcemaps optional.
Every report lands classified, summarised and prioritised, with the suspected file and line as sha-pinned permalinks. Each summary sentence links to the evidence it cites.
Sourcemaps optional
Rebase matches component names, test ids and button text against your repo.
Evidence, not paraphrase
Every summary sentence links to the console line or request behind it.
A failing test, on request
One click turns the repro into a Playwright spec that passes once fixed.
Your agent ships the fix. You review the PR.
Rebase never writes your code. It briefs Claude Code, Cursor, VS Code or Windsurf with the repro, a failing test and the files to open. Your agent raises the pull request with your credentials.
One call, the whole bundle
get_fix_bundle returns the summary, repro steps, failing test and likely files.
Fix with agent, one click
Every ticket carries a ready-made prompt for Cursor or Claude Code.
It answers in the thread
Agent replies land in the thread the reporter is watching, and resolving clears the pin.
Lands in your tracker. No second inbox.
Reports file into GitHub, Linear, Jira or Asana as native issues, mapped to the right project with the screenshot attached. Status syncs both ways.
GitHub, Linear, Jira & Asana
Native issues in the tracker your team already runs.
Duplicates don't pile up
Repeat reports link to the canonical issue.
Status stays in sync
Close it in your tracker and the pin leaves the page.
Secrets stay on the page. Only what you need.
Passwords, cards and one-time codes are never captured. Everything else masks by default and is scrubbed again server-side before the AI sees any of it.
Secrets never captured
Passwords, cards and one-time codes are blocked outright. No setting can re-enable them.
Redact any element
Hide anything with a single data attribute.
Hostile reports can't steer it
The capture is fenced and marked untrusted before the AI reads it.
Shipping every week. Here's the latest.
Pricing for all team sizes. Start free on one website.
Yearly billing saves 17%
Free
$0/mo/site
no card required
Includes:
- 1 team seat
- Invited by email, never billed. Guests file reports and follow tickets; choose commenting or read-only for each one.
- Filing caps at 50 on Free. 10 of them a month get the full AI triage; the rest file raw.
- 10 AI triages a month
- Access to integrations
- MCP hand-off
- Search across every report
- 7 days of screenshot history
Starter
$30/mo/site
billed yearly
Includes:
- 3 team seats
- Invited by email, never billed. Guests file reports and follow tickets; choose commenting or read-only for each one.
- Filing is never capped. Triage is what's metered: after 100 a month, reports keep arriving, just without the AI summary.
- 100 AI triages a month
- Access to integrations
- MCP hand-off
- Search across every report
- 30 days of screenshot history
- Not included: Catches JavaScript errors and failed requests as they happen, with the session attached. The bug reaches you before anyone thinks to report it.
Pro
Most popular$82/mo/site
billed yearly
Includes:
- 10 team seats
- Invited by email, never billed. Guests file reports and follow tickets; choose commenting or read-only for each one.
- Filing is never capped. Triage is what's metered: after 1,000 a month, reports keep arriving, just without the AI summary.
- 1,000 AI triages a month
- Access to integrations
- MCP hand-off
- Search across every report
- 90 days of screenshot history
- Catches JavaScript errors and failed requests as they happen, with the session attached. The bug reaches you before anyone thinks to report it.
Extra seats are $12/month each on Starter and Pro, prorated, whatever your billing period. Guests never cost anything.
Frequently asked questions
Paste one script tag — no API key, your domain identifies your project. Claim the site from the site itself and start on Free, no card needed. The widget on your own page is the whole product.
The pinned element, recent actions, console errors, network requests, device, deployed release and a screenshot — merged into one ordered timeline: Clicked 'Save' → POST /orders returned 500 → TypeError follows.
Every report arrives classified and summarised, with repro steps, a severity and the suspected file and line. Triage never writes code — fixing is your tools' job. Plans include 10, 100 or 1,000 triage credits a month, and if they run out triage fails open: the ticket still reaches your tracker.
Yes — that's the point. The MCP server gives Claude Code, Cursor, VS Code or Windsurf tools over your tickets; get_fix_bundle returns the summary, repro steps, the failing test and the likely files. Rebase has no write path to your repo: your agent opens the pull request with your credentials.
Neither. With a sourcemap Rebase symbolicates stack traces; without one it matches component names, test ids and button text against your connected repo to produce commit-pinned file and line links.
New tickets draft native issues in GitHub, Linear, Jira or Asana with the triage and screenshot embedded. Status syncs both ways, resolving clears the pin from the page, and duplicates are detected and linked.
Passwords, cards and one-time codes are hard-blocked — no setting re-enables them — and every other input masks by default. No session video, no DOM replay, no keystroke log. Screenshots delete at the end of your plan's retention window, and the AI reads every capture fenced as untrusted data.
Free forever on one website; Starter is $36/month, Pro is $99/month, yearly about a month free. Seats are bundled in and extra seats are $12/month. Enterprise puts several sites under one contract.
Yes — Free is free forever: 50 reports a month on one site, no card. If a paid plan ever lapses you drop back to Free with everything kept, and upgrading restores the full allowances instantly.
One script tag. Every report ready to fix.
Free forever on one site. No card, no extension, no dashboard to learn.