One extension, three triggers. Which one you reach for depends on how much is
wrong and how much you feel like typing. All three land on your board with the
evidence attached.
Reporting on a product you control? Add the bug report widget so customers can report without an account or extension.
Three modes
Pick the one that fits the bug.
One bug you can describe in a sentence: capture it. One bug you can point at: pin it. Five bugs and a bad mood: record it.
One click, the whole page
Capture
Click the extension and Toado grabs the full-viewport screenshot, console history, network HAR, JS errors, Core Web Vitals, the URL, and a DOM snapshot, then files it as a ticket on the project you pick.
Full DevTools context in one shot
Sensitive headers and tokens stripped before upload
Hit Alt+C and click. You never open the extension, and you never leave the page you are on. The composer opens in place, and the marker you leave behind is visible to the next person who lands there.
The Record button sits in the same on-page control as the pins, so you start a walkthrough without touching the toolbar. Talk while you work, and stop when you run out of things to complain about.
Up to 30 minutes per walkthrough on a paid plan, 5 minutes on free
Screen and narration, or narration only
Choose a window or tab through Chrome’s sharing picker
Use the app’s Extension page for the latest 0.2.0 build and installation steps. Chrome Web Store updates arrive after Google approves the release.
2. Sign in with OAuth 2.0 + PKCE.
No copy-pasting API keys. Your Toado account signs you in through a standard OAuth flow.
3. Capture, pin, or record on any page.
Every mode files a ticket on the board you pick, with the evidence attached and ready for your AI coding agent.
Pins belong to the screen where you placed them, including tabs and dialogs at the same address. Built-in and custom ticket types give each pin its own marker.
Works where you work
Localhost, staging, prod.
The extension doesn’t care where the bug is. Capture, pin, or record on localhost:3000
during development, on staging during QA, or on prod when a customer spots something.
Same workflow, same ticket shape, same Claude Code handoff.