
Video, network traffic, console output and the symbolicated crash thread from the session that actually failed. Captured on device, waiting in the report. Nothing to reproduce.
Various data streams recorded in a rolling buffer on the device, plus the performance and build context around them. When something fails, they arrive together.
Pixel-accurate replay of what the user actually saw, frame for frame.
Every request and response, inspectable down to headers, payload and timing.
System console plus your own log lines, in true chronological order.
Symbolicated stack traces, sitting next to the recording that produced them.
Taps, gestures and the active screen, overlaid on the video.
Mark views and fields as private and the pixels never leave the device.
Android reports ANRs out of the box; opt-in detectors on iOS and Android catch hangs, rage taps, main-thread misuse and HTTP errors, each with its full session.
On iOS and Android: startup, screen-load, network and file I/O timings, attached to every report.
A read of the evidence, and of the crashing code once a repository is connected, with a likely root cause.
Release builds tracked with resolved-dependency changes and automatic vulnerability scans, plus opt-in size analysis.
Bugsee.notify() sends a message to your messaging integrations without filing an issue. In beta on Android.
Users shake to report, and the recording is already attached.
Scrub back through the seconds before failure. Video, console, requests and the crash thread all move on the same clock, so cause and effect line up instead of being guessed at.
Add the SDK, paste a token, ship. The same call on every platform — no build step, no proxy, no instrumenting your views.
The MCP server gives any MCP-aware agent scoped access to crashes, errors, builds and vulnerability scans — from inside the editor. Bugsee never receives your source code through MCP: your assistant reads your files locally, and your AI provider's data policy applies.
Read the MCP documentation →No agent to wire up: the analysis works from the crash report out of the box, names the likely cause and proposes the fix, inline in the issue. Connect a source repository (optional, read-only) and it also reads the code around the crashing frames, which is processed by AI.
Force-unwrap of data.orderId when /v1/checkout returned 500.
Drop in the SDK today and the next failure arrives with its own evidence.