In-app bug reporting for web and mobile apps.

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.

Bug reporting software collects bug reports from customers, testers or your own team together with the context engineers need to fix them: what happened, on which page, device and browser, and the technical data behind it. Gleap collects reports inside your web or mobile app, so each one arrives with a marked screenshot, console and network logs and device data, and can go on to Jira, Linear or GitHub. Compare options in the best bug reporting tools.

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 customer-reported bugs. 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 issues there.

Yes. Gleap.sendSilentCrashReport sends a report with a description and a priority but no form. By default it attaches the logs and metadata and leaves out the screenshot, the replay and attachments; its third argument sets what is excluded. 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.

It lands in the inbox as a ticket your team can answer, assign and track. From Team, with the Investigate bugs skill on, Kai Support investigates each new report from the widget before it reaches the inbox: it reads the logs, the click trail, the screenshot and any screen recording 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 a confidence level and the files it read. Feature requests belong in your customer feedback software, where customers vote on them.

Yes, on Team and up. Kai Code starts the coding task on its own when you allow it, or a teammate starts it: it plans the change, edits the code, runs the tests and opens a pull request linked to the ticket. Your engineers review and merge. Once a teammate confirms the fix is live, 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 leads to a finding, 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. See the whole workflow in AI customer support for SaaS.

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. On Android, network requests are logged with Gleap.logNetwork or the OkHttp interceptor. Shake to report is available on iOS and Android.

Yes. Those apps run on the web, so the JavaScript SDK captures the same screenshot, replay, console and network logs. Kai Code can ask the platform's agent to install it, and from Team it asks the same agent for the fix. See Gleap for vibe-coded apps.

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 on Team and up Kai Support investigates them with the logs, account data and your code.

They all capture bug reports with screenshots and context. Gleap adds what happens next: reports land in the same inbox as your customer conversations, and on Team and up Kai Support investigates them with the logs, the click trail and your code, and confirmed bugs become pull requests through Kai Code. Switching from one of them? Compare Gleap vs Instabug, Gleap vs Marker.io, Gleap vs Usersnap, Gleap vs BugHerd and Gleap vs Userback.

No, but every plan starts with a 7-day free trial. Starter is $29 per month billed annually ($35 monthly): in-app bug reporting on web and mobile with the marked screenshot, console and network logs, device data and custom data, for one seat and one project, plus live chat, Kai Support and Kai Copilot, with no ticket limit and the full ticket history. Team ($149 per month billed annually, $179 monthly) adds unlimited seats and projects, session replay, integrations such as Jira, Linear and GitHub, Kai Support's investigations and Kai Code. Kai Support is billed by the AI it uses: an estimated under $0.05 per resolution, or about $0.35 with deep code investigations, against Intercom Fin's $0.99. See pricing.