Skip to content
Showbug

Pre-launch · waitlist open

Show the bug.
Skip the back‑and‑forth.

Showbug is a button you embed in your app. Your user clicks it and talks to a voice AI agent while their screen and mic are captured. Your developers get a ticket with the recording attached.

We'll only use your email to tell you when early access opens. We also record your browser, device type and country to understand who's interested. We never store your IP address.

Where it stands. The widget, capture and a session dashboard with replay work today. AI-written tickets and delivery to Linear, Jira or a webhook are still being built.

recording.webm · 1:12example ticket

Invoice export fails on invoices with no line items

app.example.com/billing/invoices

Repro steps
  1. Open Billing → Invoices.
  2. Create a new invoice and leave it empty.
  3. Click Export. Nothing downloads.
Console
TypeError: Cannot read properties of undefined (reading 'lineItems')
Said by the reporter

Agent: Does it happen on every invoice?

User: Only the ones I just created.

Illustrative example written by us. Not a real customer report.

From “something is broken” to a ticket, in three steps

  1. Step 1

    Add one script tag

    Drop the Showbug snippet into your app. It adds a small report button and loads the rest only when someone clicks it.

    <script src="…/loader.js" data-key="pk_…">

  2. Step 2

    The user shows and tells

    They click the button and the browser asks for screen and mic access. A voice agent asks what went wrong, then follows up on whatever is still unclear while they point at it on screen.

    “Does it happen on every invoice?”

  3. Step 3

    Your developers get a ticket

    Capture stops when the user is done. The session becomes a ticket for your tracker, with the recording and the context attached.

    Linear · Jira · webhook (planned)

A ticket a developer can start on

The goal: no second conversation with the reporter. This is what each ticket is built to contain.

Summary
What broke and where, in a sentence or two.
Repro steps
Built from the user's clicks, page changes and what they said.
Expected vs. actual
As the reporter described it, with the follow-up questions already asked.
Page and user
URL, browser, and who they were if your app identifies them.
Console and network
Recent console errors and failed requests, length-limited.
Recording
Screen and voice with a transcript, plus a replay of the page in the dashboard.

Who it's for

Not for yet: products that handle payments, health, banking or credentials on screen. We would rather say so now.

  • SaaS teams with a browser app and signed-in users

    The first pilots target teams of roughly 5 to 50 engineers who lose hours asking customers what they were doing when it broke.

  • Support and QA who relay bug reports

    Stop forwarding “it's broken” with a screenshot. The follow-up questions get asked while the reporter is still on the page.

  • Engineers who reproduce bugs from a one-line message

    Open the ticket, watch what happened, read the console error, and start on the fix.

Questions, answered plainly

Does it record without asking?

No. Nothing is captured until the user clicks the button and then approves the browser's own screen-share and microphone prompts. They choose what to share, and they can stop sharing at any time.

What about passwords, card numbers and other sensitive data?

Form inputs are masked in the page replay, and anything you mark with data-private is left out of replay and click capture. The screen recording is different: it contains whatever pixels are on screen, and masking the page does not hide those. Pixel-level redaction is not built yet, so we advise keeping Showbug off pages that show payment, health, banking or credential data.

Who else sees the audio and the screen?

The voice agent runs on a third-party realtime AI provider, so microphone audio and screen frames are sent to it during the conversation. Today that is OpenAI's Realtime API.

Which browsers and trackers will it support?

Desktop Chrome first. For tickets, we are building delivery to a webhook and to Linear and Jira. Which ones ship first depends on what the waitlist teams use.

How much will it cost?

Not decided yet. Every session runs a voice model, so pricing will be based on usage, and we are still measuring what a session costs.

What happens when I join the waitlist?

We store your email and use it to tell you when early access opens.

Get early access when it opens

Join the waitlist and we will email you once, when Showbug is ready for the first teams.

We'll only use your email to tell you when early access opens. We also record your browser, device type and country to understand who's interested. We never store your IP address.