Screenshot + console + browser context
Bug reports · Early access
Bug reports,
with the context.
A small widget that turns vague reports into screenshots, console logs, and a clean handoff to your issue tracker. Built for teams that ship.
See what arrives
What users report. What your team receives.
The widget turns a point-and-click complaint into a report with the evidence already attached. No screenshot chase, no missing browser details, no guessing.
- Screenshot
- Selected element
- Console logs
- Network state
- Replay steps
Beta proof
Public proof points, not placeholder customer logos.
GitHub Issues first
$7.99/month flat
Chapter 01 · The widget
Three things, done properly.
We're not a do-everything tool. Capture, context, handoff - and we sweat the details on each.
Capture
Users click the widget, point at the broken element. You get a pixel-perfect screenshot and the exact CSS selector - no back-and-forth.
Context
The last 50 console entries, browser, OS, viewport, and current URL travel with the report. Everything you'd ask for, already attached.
Handoff
One click sends a structured issue to GitHub. Your team picks it up in their normal flow - no new tool to babysit.
Chapter 02 · Install
A widget that disappears until you need it.
Paste two lines into your HTML. Your domain is auto-detected. Reports route to the repo you connected - that's the whole setup.
- A single script tag. No SDK, no build step.
- Shadow DOM rendering. Zero CSS conflicts with your site.
- Lazy-loaded, async, ~12kb gzipped. Doesn't touch your perf budget.
<!-- That's it. Really. -->
<script>
window.ContextCaptureSettings = {
projectKey: "PROJECT_KEY",
position: "bottom-right"
};
</script>
<script src="https://widget.contextcapture.ai/widget/PROJECT_KEY" async></script>Chapter 03 · The inbox
One screen your team actually opens.
Every report lands in a quiet inbox - sorted, filterable, with the full context one click away.
Checkout button unresponsive on iOS Safari
Needs reviewPricing toggle resets after locale switch
ScheduledHero image overflow on 1280px
ShippedConsole error on /signup - undefined token
Shipped
Chapter 04 · The contents
Everything that travels with the report.
Five small details that turn "the button doesn't work" into a real, fixable issue.
Never ask again
Automatic screenshots
Users click, you get a pixel-perfect screenshot. No more 'can you send a screenshot?' - it's already attached.
Debug instantly
Console logs included
The last 50 console entries with full stack traces. No more asking users to open DevTools.
Point & click
Element selection
Users click directly on the broken element. You get the CSS selector, HTML snippet, and computed styles.
No more guessing
Browser context
Chrome? Safari? Mobile? Desktop? URL, viewport, user agent, and device info - captured automatically.
Full journey
Session recording
Periodic screenshots, DOM snapshots, and user interactions. Replay the whole journey to the bug.
Chapter 05 · Session recording
Replay the journey, not just the crash.
Periodic screenshots and interaction snapshots make the report feel like a concise movie of what happened.
"The fastest bug report is the one that already has the screenshot, logs, and browser context attached."
Chapter 06 · Pricing
Honest pricing, no surprises.
Start free. Upgrade when your team is sending more reports than you can keep up with.
Special beta pricing
Appendix · FAQ
Straight answers.
How much does it cost?
Start with a 14-day free trial, then a flat $7.99/month - unlimited projects, unlimited bug reports, up to 5 team members. No per-seat pricing.
How long does setup take?
About a minute. Add a script tag to your HTML. Your domain is auto-detected and reports route to the repo you connect.
Will it conflict with my CSS?
No. The widget renders inside a Shadow DOM, fully sandboxed from your site. Works alongside Tailwind, Bootstrap, or anything else.
What is captured?
A screenshot, the last 50 console entries, selected element details, browser/OS/viewport, current URL, and JavaScript errors.
Colophon
Drop in the script. See what arrives.
Two lines of HTML and your team's bug reports start landing with screenshots, console logs, and the full browser context already attached.