Rebase + GitHub. Bugs become issues.
Every report files into GitHub as a structured issue in the right repo — full engineering context attached, and status synced both ways.
Connect your repo
Install the integration and pick which repository reports should file into.
Reports become issues
Every capture opens as a GitHub issue — formatted, labelled and ready to pick up.
Close it once
Close the issue in GitHub and the Rebase ticket closes with it. Both sides stay honest.
// In your repo
Where the code lives.
Bugs get fixed next to the code that caused them. Rebase files issues straight into your repository the moment a ticket is created — with the screenshot inlined and a link back to the full report.
- Structured issues, not pasted screenshots
- Labelled rebase — plus bug, enhancement or question
- AI triage — summary, severity, repro — in the body
[Rebase] Pay now button does nothing on checkout
opened by rebase · ready to pick up
// Points to the fix
Starts at the suspected file.
Because Rebase knows your repo, triage names the likely source file right in the issue — so whoever picks it up starts in the right place.
- Suspected source location, matched to your repo
- Map priority and status onto your labels
- A #badge on the ticket jumps straight to the issue
// The details
Everything travels with the issue. Attached automatically.
- The exact browser, OS and viewport
- Console errors and warnings, as they happened
- Failed and slow network requests
- A full-page screenshot from the moment it was flagged
- The exact clicks and inputs that led to the bug
- The flagged element, its selector and component name
- AI triage: a summary, a severity and the likely source
- A link back to the full Rebase report
Frequently asked questions
The Rebase ticket resolves and its pin leaves the page. Reopen the issue and the ticket reopens — status syncs both ways, and each direction is toggleable.
The flagged element, the last 50 user actions, the last 50 console errors and warnings, the last 50 network requests, a device and environment snapshot, and a screenshot — merged into one time-ordered timeline: Clicked 'Save' → POST /orders returned 500 → TypeError follows.
Rebase runs on public HTTPS domains — production and staging. On localhost the widget explains itself in the console instead of failing silently, so the tag is safe to keep in development.
// More integrations
Works with the rest of your stack. One layer, every tool.
Start shipping feedback faster.
Start your 7-day free trial.