Squash turns "it's broken" into a complete bug report — annotated screenshot, console and network logs, and a session replay of the last minute — filed straight into GitHub before your user finishes their coffee.
One script tag. No SDK, no build step: <script src="…/widget.js">
Drop widget.js into your site or staging build. The reporter button appears; console, network and replay capture start quietly in the background.
Clients, QA, or users click the button, mark the broken bit on an auto-captured screenshot, and hit Squash it. No accounts, no screenshots-by-email.
The report lands in your Squash inbox — and as a GitHub issue in the repo you picked — with logs, environment, and a replay of the last minute attached.
Every report arrives with the context a developer would have asked for — captured automatically at the moment it happened.
The page is captured the instant the reporter clicks. They drag to highlight exactly what's broken — no more "see attached, circled in red."
The last 200 console lines, uncaught exceptions and promise rejections ride along with every report, stack traces included.
Failed fetches and slow XHRs are recorded with method, status and duration — so "it won't load" comes with the 500 that caused it.
A rolling buffer keeps the last ~90 seconds of the session. Watch exactly what the reporter did — every click, scroll and keystroke, inputs masked.
Pick a repository per project and Squash files the issue for you — screenshot embedded, console attached, labeled and linked back to the full report.
Invite your whole team for $5 a seat. Filter by project and status, set severity, comment, and close bugs where they were reported.
Squash keeps a rolling replay buffer while your site runs. When someone reports a bug, the last minute and a half is attached — pixel-accurate DOM playback, not video.
Every feature, every plan — because there's only one plan.
5 teammates × $5 = $25/mo. Seats sync as your team changes.
The script loads deferred and weighs about the same as one hero image. Replay capture uses rrweb's incremental snapshots — a rolling buffer in memory, nothing uploaded until someone actually reports a bug.
All text inputs are masked in replays by default, and you can exclude any element by adding the squash-block class. Screenshots are taken only when the reporter clicks the button, and they see exactly what's being sent before submitting.
Connect a GitHub token in workspace settings, pick a repository per project, and choose automatic or one-click issue creation. Issues arrive with the screenshot embedded, console output collapsed, and a link back to the replay.
No. Anyone using your site can file a report — clients, QA testers, beta users. Only your team members who triage bugs need seats.
Yes — each project has its own widget key, and you can restrict which origins may submit reports. Most teams run one project per site or environment.
14 days free · $5/user·month after · cancel anytime