// Platform — Triage & AI
More than a screenshot. Points to the fix.
Rebase triages every report — a summary, a severity and the likely source — deduplicates it, and hands your tools a clean, structured payload.
A report arrives
Someone flags an issue and Rebase captures the full session context around it.
Triage runs automatically
A summary, repro steps and a severity with a confidence score — and a classification: bug, change request or question.
It points to the fix
Matched against your connected repo, the ticket names the likely source file before an engineer even opens it.
// Signal, not noise
Deduplicated by default.
Ten people hitting the same bug shouldn't mean ten tickets. Repeat reports are matched and linked — your queue stays a list of problems, not a list of complaints.
- Sentences link to evidence — click the 500 and it opens
- Bug, change request or question — formatting adapts to each
- Change requests keep the exact 'from → to' strings, verbatim
Rebase TriageRB-128Order creation fails — likely unhandled error in createOrder()
triaged before anyone opened it
// The Debug view
The investigation, in the thread.
Any ticket thread morphs into a Debug panel — the AI triage on top, tabs for steps, console, network and environment underneath, and the suspected source. In the widget, on the page. No dashboard.
- Stacks symbolicated against your public sourcemaps
- Matched to your GitHub repo — a file:line, not a minified frame
- Re-run triage on demand — one credit, summary only
// The details
What triage adds to a ticket. On top of the capture.
- A plain-English summary, repro steps and a severity with confidence
- Classified as bug, change request, question or other
- Duplicates matched over 90 days and linked to the canonical ticket
- AI titles only replace derived ones — never a human's words
- Summaries in English; quoted errors stay verbatim and searchable
- The AI reads a scrubbed, size-budgeted slice — never the raw payload
- A no-signal gate: empty reports never burn a credit
- Fails open — without credits, tickets still reach your tracker
Frequently asked questions
One credit is one AI-triaged ticket — search, duplicate matching and embeddings are free. Every project includes 200 credits a month, with a live meter in Settings, owner emails at 80% and 100%, and a refund if the model call fails.
Tickets are embedded semantically and matched against the last 90 days. Near-duplicates are marked and linked to the canonical ticket — detected and linked, not silently dropped — and the canonical tracker issue gets a cross-reference comment.
Stack traces are symbolicated against your public sourcemaps and matched to your connected GitHub repo, so tickets carry a file:line suspicion — not just a minified stack.
Triage fails open. The ticket still flows to your tracker un-enriched, and owners can re-run triage on any ticket once credits refill.
// Keep exploring
The rest of the platform. It all works together.
Capture
Click to report — console, network, steps & a screenshot.
Detected issues
Uncaught errors from real sessions, queued for review.
Collaboration
Pins on the live page — threads, mentions & roles.
Issue-tracker sync
Files into GitHub, Linear, Jira & Asana. Two-way status.
AI agents (MCP)
Five MCP tools with scoped, revocable tokens.
Team & notifications
Invites, roles, unlimited users — mentions instant, the rest digested.
Privacy & security
Masked by default, scrubbed twice, isolated per tenant.
Start shipping feedback faster.
Start your 7-day free trial.
The hero title fails to render — fires while returns 500, so the layout never settles.
The likely source for the issue is located in these files:
Generated from the capture — verify before relying on it.
sess_3kf9d2req_a81c0e[email protected]v0.9.1v0.1.0