Rebase 1.0

First public release. One script tag adds a reporting widget to any site: anyone can flag an element, and the report files into your tracker.

#Capture

• Flagging an element on the live page captures the session around it: the last actions, console entries, and network requests, merged into one time-ordered timeline.
• Reports carry a screenshot from the moment of the click and a device and environment snapshot.
• Dead clicks and rage clicks are detected and labelled.

#Triage

• Every report arrives with a summary, a severity, and the suspected source, matched against the connected repo down to the file and line.
• Repeat reports are detected and linked to the original instead of piling up as duplicates.

#Trackers

• GitHub, Linear, Jira, and Asana are supported. Reports file themselves as structured issues in the right project.
• Status syncs both ways — close the issue in the tracker and the report closes in Rebase.
• Slack posts new and resolved tickets to a channel.

#Detected issues

Uncaught errors from real visitor sessions are collected and queued for review, with the same captured context attached as a reported issue.

#Threads and roles

Reports are pins on the live site. Each one opens a thread with mentions, and roles and invites control team access.

#Privacy

• Everything typed is masked before it enters the capture buffer.
• Password, card, and one-time-code fields are never captured at all.
• Reports are scrubbed a second time server-side.
• Every customer's data stays isolated to its own tenant.

#MCP server

The MCP server exposes full ticket context — console, network, steps, suspected source — to Claude Code, Cursor, or any MCP client.

#Install

Add the one-line script tag and claim the site with a meta tag. No API keys.