Capture. Every report carries the visit behind it, with a replay if you want one.
Context on what happened, whether your team or customer reports it.
Rebase records the clicks, failed requests and errors behind every report. Engineering gets something they can reproduce, and support stops asking customers for steps.
Bring your agent
and let it start from what happened.
Continue button does not open checkout
What they saw
acmeShopJournalHelpCart 1
Checkout
DetailsPaymentConfirmation
ContinueYou won’t be charged yet
Order summary
Arc desk lampOat · Qty 1£89.00
Subtotal£89.00
Shipping£5.00
Total£94.00
0:00 / 0:54
4×
Summary AI
Clicking “Continue” calls /api/checkout, which fails with a 500. The page shows nothing, so they clicked four more times, then reported it.
What happened
Show 3 earlier
Interactive demoClick any step in What happened to jump the replay.
From “it’s broken” to fixed. Without the back-and-forth.
Every report arrives with the visit behind it, written up in plain words and sent where your team already works.
Understand. A plain-words summary, the likely cause and where to look.
Fix. An issue in your tracker, ready for your team or your coding agent.
For QA and engineering. Reports you can reproduce on the first read.
Every report arrives with the exact sequence that broke, and a pointer to the code.
See exactly what happened with pages, clicks, failed requests and errors in order.
Watch the last minute and jump straight to the moment it broke.
Start where the bug is with the likely file and line, when source maps are available.
One issue, not twelve, with every repeat counted on the original.
Report bugs while you test by pointing at the broken element on staging.
Let your agent take the first pass over MCP, from Claude Code, Cursor or any MCP client.
For support. Stop asking customers for screenshots.
Get the whole story from one link, and hand engineering something they’ll actually pick up.
Customers say it in their own words, and Rebase attaches the technical side.
Send one link instead of five questions when a report needs more detail.
Ask from Slack with /rebase, right where the conversation is.
Read it in plain words, with the technical details one switch away.
Escalate in one click to GitHub, Linear, Jira or Asana, with everything attached.
Customers stay in control, and nothing is shared until they choose.
Private by default. Typed values never show.
Replay is off until you turn it on, page text stays masked unless you show it, and customers choose what they share.
Anything they type stays hidden in reports, packets, screenshots and replays.
Page text and images, too, unless you choose to show them.
Replay is off until you turn it on, and every replay is gone within 30 days.
One snippet, then you’re done. Nothing to build or bundle.
Paste it into your layout or your site builder, connect a tracker, and the next report arrives with what happened.
Copy the snippet, publish, check. Rebase confirms it’s live, and any site builder works.
Works with
GitHub
Linear
Jira
Asana
Slackand any MCP client
Questions, answered.
Anything else, write to support@rebase.dev.
From the “Report a problem” button Rebase adds to your website. They say what went wrong in a sentence, and Rebase attaches the pages, clicks and errors that led up to it. They don’t need an account.
Plans from $69 a month, with unlimited websites and teammates.
See pricing