Rebase is here

New

• The widget. Customers open it with a keyboard shortcut, a link, a floating "Report a problem" button or a button of your own, then say what went wrong in a sentence. They don't need an account.
• What happened. Each report carries the recent pages, clicks, failed requests and console errors, the browser and device, and a screenshot from when the widget opened. Before sending, the customer can leave out anything except their browser and device.
• Replay. Turn it on for a website and reports include a replay of the last 30 to 60 seconds. Page text and images stay hidden unless you choose to show them, and replays are kept for 30 days at most.
• Privacy. Typed values are always masked. Password, payment card, one-time code and phone number fields are never captured, and one attribute hides anything else you mark.
• AI triage. Every report gets a short summary, a type and a priority, labelled as AI. For a bug it can ask the customer one follow-up question. It never resolves a report or decides where one goes.
• Where to look. When a report has a JavaScript error or a selected element, Rebase points at the likely source files, using your website's source maps and your GitHub repository.
• Trackers. Reports become issues in GitHub, Linear, Jira or Asana as soon as they arrive, and closing the issue resolves the report. When the same problem is reported again, Rebase adds a comment to the original issue rather than opening a new one.
• Packets. When a description isn't enough, support sends the customer a packet link. They open it on your website, share their recent visit or try again, and you see what happened. Request one from the Inbox, from Slack or by mentioning Rebase on a GitHub or Linear issue.
• Slack. New reports post to a channel, and /rebase requests a packet without leaving the conversation.
• MCP. Claude Code, Cursor and other MCP tools read your reports through five read-only tools. Your agent changes the code with its own tools, and Rebase never touches it.
• Your team. Owner, Admin and Member roles, with sign-in by email code or Google. Customers never see your Inbox or anything your team adds.
• Setup. Paste the snippet into your layout or website builder, and Rebase checks that it's live. Test, staging and local websites each get their own check.