Skip to content
Toado
Log in Start free
Embedded bug reporting

Put a bug report button inside your product.

Add one project-specific script to your site. Customers report what went wrong without a Toado account, and your team receives a ticket with the screenshot, page context, console errors, and debugging evidence attached.

Add Toado to your site See how the widget works

Included with Toado Team. External reporters do not need paid seats.

Toado bug report dialog with description, email, session history, and send report controls
On the page where it happened

A reporting path built into the product.

Toado project board with the report a bug launcher highlighted in the toolbar
The launcher stays close to the work and opens the report experience on demand.
From report to fix

Your customer sees the bug. Toado brings your team the evidence.

Ordinary feedback forms tell you something broke. Toado captures the state around the failure and sends it to the selected project as a triage-ready ticket.

1

Install once

Copy the snippet from Project Settings and add it wherever people should report bugs.

2

Report in context

A customer describes the problem and submits without leaving the page or creating an account.

3

Triage and ship

The ticket arrives with evidence. Assign it to a teammate or hand it to an AI coding agent.

Project widget settings showing installation, snippet detection, approved sites, and a live preview
Project Settings gives each widget its installation snippet, detection status, approved sites, and preview.
Context-rich reports

The context engineering usually has to ask for, captured up front.

Page screenshot

A DOM-rendered view with the Toado launcher and dialog removed.

Browser context

Page URL, viewport, browser details, and the reporter's description.

Console and JavaScript errors

Messages and failures that help explain what the reporter saw.

Network evidence

Timing and request data, with deeper capture available as an explicit opt-in.

Reporter details

Optional email collection and project-specific questions when follow-up matters.

Automatic ticket creation

Every report enters the selected project ready for triage.

Capture note: Widget screenshots are rendered from the page itself. Video, WebGL, cross-origin iframes, and some canvas content may not reproduce exactly. Use the Chrome extension when browser-level fidelity or capture on an uninstrumented site is required.

Make it yours

Your bug button should look like it belongs there.

Choose a floating button, edge tab, inline launcher, or no visible launcher. Configure the label, icon, colors, placement, dialog, and mobile behavior with a live preview.

  • Modal or pinned-panel reports
  • Site-based theme generation plus manual control
  • Optional draggable launcher
  • Open from your own button or menu
Two workflows

One snippet. Customers and teams.

For customers and external testers

No Toado login or browser extension. Optional email and custom questions collect the follow-up details your team needs.

For the people building the product

Use shortcut-driven capture on products you control. Keep the extension for every other site.

Widget appearance settings for launcher style, icon, label, position, and live preview
Widget Studio keeps launcher and dialog controls beside a live preview.
Controlled by you

Public to reporters. Restricted to approved sites.

Each project has its own key and site rules. Toado detects installations and helps owners approve origins before accepting reports.

  • Project-specific public widget key
  • Origin rules for approved sites
  • CAPTCHA and submission rate limits
  • Sensitive-data filtering
  • Generated Content Security Policy guidance
  • Immediate off switch and key rotation

Review Toado security controls

Widget or extension

Use the widget where you own the product.

Bug report widget
Best for customers and teams on a product you control. No reporter account, one site snippet, in-page capture.

Chrome extension
Best for authenticated team members on any site. Installed per user with browser-level capture.

Most teams use both: frictionless customer reporting inside their products and authenticated capture everywhere else.

Company widget overview listing projects with setup and live installation statuses
Owners can review setup and installation status across projects.
Widget capture settings showing minimal, standard, and deep evidence collection levels
Capture levels make standard and opt-in deep evidence collection explicit.
Report in, ticket out

The reporter sees continuity. Engineering gets the evidence.

A reporter can see the reports created during the current session. On the Toado side, each submission arrives as a normal ticket with its screenshot and debugging context ready for triage.

Bug report dialog showing a previous report from the current visitor session while another report is being written
Session history gives the reporter a reference for submissions made during the visit.
A widget-created Toado ticket with the submitted description, page screenshot, and debugging context
The resulting ticket includes the report, captured page, and technical evidence in Toado.
Complete the loop

A customer report can become an agent-ready task.

Toado's MCP connector lets Claude Code, Codex, Cursor, Cline, and compatible agents read the report, inspect evidence, comment, and move the ticket through review.

Customer reports → Toado captures → Agent investigates → Team reviews → Fix ships

See AI coding with Toado

Put your next bug report where it can get fixed.

Start a Toado Team workspace, create a project, and copy its bug report widget into your site.

Start freeRead the setup guide