Bug Analyst logo

From embed to merged fix

Six steps — the first three take about five minutes, the rest happen on their own.

index.html
Widget is live
1

Create a widget

Sign up free and add a widget — just a name and the domain it lives on. Each widget gets its own embed code, settings and integrations, so agencies can keep every client separate.

2

Paste one script tag

Copy the embed code from the dashboard and paste it before </body>. A floating report button appears on your site instantly. No npm install, no build step, no backend changes — it works on any stack.

<script src="https://api.buganalyst.com/widget/script.js"
  data-widget-id="w_your_widget_id"
  data-api-url="https://api.buganalyst.com"></script>
3

Connect your tools

In the widget settings, connect Slack (pick a channel), Trello (pick a board and list), and GitHub (pick the repository behind your site). Each takes one OAuth click — no API keys to copy around.

4

Users report bugs in context

A visitor hits a problem, clicks the button, and writes two sentences. Behind the scenes the widget has already captured the JavaScript errors, their click journey, failed API calls, browser details and the page URL. They can attach a screenshot or short video too.

5

AI proposes the fix

Open the report in your dashboard and click “Analyze with AI”. Buganalyst locates the relevant files in your connected repository, identifies the root cause, and shows you a plain-English explanation with a line-by-line diff and a confidence rating.

6

One click opens the pull request

Happy with the fix? Click “Create pull request”. Buganalyst opens a branch and a PR on your repo with the full bug context in the description. When you merge it, the report is marked resolved automatically. Not happy? Dismiss it and fix it your way — the captured context still saves you the diagnosis.

What lands in your Slack channel

A reporter writes two sentences. Your team receives all of this:

# bug-reports

Buganalyst is posting
B

Buganalyst APP

🐛 Checkout button crashes on click

yoursite.com/checkout · Chrome on macOS

TypeError: Cannot read properties of undefined

Delivered in 1.2s — journey & errors attached

Title, description and reporter email
Page URL where the bug happened
Browser, OS, viewport and zoom level
Captured JavaScript errors with stack traces
The user's click and navigation journey
Failed API calls with status codes
Screenshot or screen recording, if attached
Link to the full report in your dashboard

Five minutes to set up. Free to start.