In-app bug reporting with session replay.

In-app bug reporting lets a customer or tester report a bug from inside the product, on the screen where it happened. With Gleap, the report carries a marked screenshot, session replay, console and network logs, browser and device data and the custom data you attach, so your team can investigate without asking for steps to reproduce.

A session replay bug report contains a recording of what the customer did before reporting: page changes, clicks, scrolling and input, replayed in the ticket with click markers on the timeline. The JavaScript SDK records the minutes before the report and keeps password inputs masked by default. The iOS and Android SDKs build a replay from periodic screenshots.

Browser and version, operating system, screen size and pixel ratio, current URL, language, SDK version, app build and release version, session duration and whether the device is mobile. Console logs (up to 500 entries), the last network requests with method, status, duration and payload, custom events from Gleap.trackEvent and the custom data you attach with Gleap.identify or Gleap.attachCustomData.

The widget's Report an issue form has a Mark the bug button. It opens a screenshot of the current page in an editor with a rectangle tool, a pen, a blur tool for private content, a color picker and undo. The customer marks the spot, presses Next and describes what went wrong. A Record screen option captures a short screen recording instead.

Password inputs are masked by default in session replay. You can mask all inputs with Gleap.setReplayOptions, and mark elements with the rr-mask or rr-block classes. For network logs, a blacklist excludes endpoints and filters remove headers and payload keys. Console logs are capped at 500 entries and network logs at 30 requests. See the masking guide and Gleap trust.

Both, for the reporting side. Reports arrive as tickets on a bug board with type, status (Open, In progress, To test, Done), priority, assignee, tags and due date. Your team replies to the reporter from the same ticket, and integrations push the report to Jira, Linear, GitHub, Asana, ClickUp or Azure DevOps when engineering tracks work there.

Yes. Gleap.sendSilentCrashReport sends a report with a description and severity but no form, with the same logs, replay and metadata attached. Use it for caught exceptions and failed requests. Gleap.trackEvent adds custom events to the timeline, and Gleap.preFillForm fills the form with what your app already knows.

With bug triage on, Kai Resolve investigates each new bug report before it reaches the inbox: it watches the replay, reads the logs and, when you allow it, your code read-only. The ticket arrives classified as answerable, confirmed bug, suspected bug, feature request, needs more info or inconclusive, with confidence and evidence attached.

Yes. A teammate picks up the coding task with Kai Code: it plans the change, edits the code, runs the tests and opens a pull request linked to the ticket. Your engineers review and merge. After the release, the customer who reported the bug hears back in the same conversation. That is how Gleap closes the loop.

It is the input. In self-driving development, a customer report becomes evidence, the evidence becomes a verdict, a confirmed bug becomes a coding task and a pull request, and your team reviews what ships. Reports from the Gleap SDK carry the most evidence, because replay, logs and device data are captured automatically.

Web through the JavaScript SDK, iOS and Android through native SDKs, and React Native, Flutter and Capacitor through wrappers around the native SDKs. Session replay with page changes is a web feature; the mobile SDKs capture screenshots, console and network logs, device data and a screenshot-based replay. Shake to report is available on iOS and Android.

Same SDK, same report, a different job. The website feedback tool is for visual QA: reviewers, clients and customers mark layout, copy and design issues on a screenshot of the page. In-app bug reporting is for defects in a product: the replay, logs and device data matter, and Kai Resolve investigates them.

All four capture bug reports with screenshots and context. Gleap adds what happens next: reports land in the same inbox as your customer conversations, Kai Resolve investigates them with replay, logs and code, and confirmed bugs become pull requests through Kai Code. Compare the details on the Instabug, Marker.io and Userback alternative pages.

In-app bug reporting with session replay, console logs and custom data is included from the Team plan, with unlimited seats. Kai Resolve and Kai Code are part of Pro, with AI usage billed by tokens and model. See pricing.