How Crosscheck Works
Crosscheck replaces the back-and-forth of traditional bug reporting with a single capture that includes everything a developer needs to understand and fix the issue. Here is how the workflow fits together from end to end.
The capture-to-resolution flow
┌──────────────────────┐
│ Chrome Extension │
│ │
│ Screenshot │
│ Recording │
│ Instant Replay │
│ + Developer Context │
└───────────┬───────────┘
│ capture
▼
┌──────────────────────────────────────────┐
│ Web Dashboard │
│ │
│ Projects ─► Checks ─► Detail View │
│ Video player + devtools panel │
│ Comments, tags, filters │
│ Public links & team sharing │
│ Jira & ClickUp integrations │
└───────────────────────────────────────────┘Step by step
Install the Chrome Extension
Add Crosscheck from the Chrome Web Store and pin it to your toolbar. Sign in or create an account directly from the extension popup.
Capture a bug
When you encounter an issue during testing, open the Crosscheck extension and choose a capture mode:
- Screenshot — Capture the current page and annotate it with drawing tools.
- Screen Recording — Record your tab or desktop, then trim to the relevant section.
- Instant Replay — Grab the last 1–5 minutes as a lightweight DOM replay, even if you did not start recording beforehand.
Developer context is captured automatically
While you interact with the page, Crosscheck silently collects developer context in the background. When you create a capture, the following data is attached automatically:
- Console logs — Errors, warnings, and info messages from the browser console.
- Network requests — Every HTTP request and response, including status codes and timing.
- User actions — A timeline of clicks, keypresses, and navigation events.
Your capture is saved securely
Captures are securely uploaded and available on your dashboard within seconds. Screen recordings that need trimming are processed automatically before they appear.
Share with your team
Every capture (called a "check" in Crosscheck) can be shared in two ways:
- Public link — Generate a shareable URL that anyone can view without logging in.
- Team invitation — Invite specific users by email to view the check within the dashboard.
You can also push captures to Jira or ClickUp through built-in integrations.
Review in the dashboard
Open app.crosscheck.cloud to browse checks organized by project. The detail view shows the capture alongside a tabbed devtools panel with console logs, network requests, and user actions. Developers can see exactly what happened — no more asking "what were the steps to reproduce?"
What makes this different from a screenshot tool?
A screenshot alone rarely tells the full story. Crosscheck attaches the developer context that would otherwise require a developer to manually open devtools and try to reproduce the issue. Console errors, failed API calls, and the exact sequence of user actions are all included automatically. This turns a vague "it's broken" report into an actionable, self-contained bug report that a developer can diagnose without leaving the dashboard.