Hit Record.
Open the pin control on any page and press Record. The extension records the tab and your microphone. No account for the page, no setup on the site, works on localhost.
New Walkthrough recording
Say what’s wrong. Get the tickets.
Record a walkthrough of your app, point at what’s broken, and talk. Every pin you drop becomes a ticket with a screenshot, the element you pointed at, and your words as a transcript. Your AI coding agent reads it and starts on the fix.
Included on every plan. Up to 30 minutes per walkthrough on a paid plan, 5 minutes on the free plan. Works on localhost, staging, and prod.
Walkthrough demo A two-minute recording of a walkthrough turning into tickets. Video coming soon.
Why record
A screenshot shows the bug. A walkthrough explains it.
The hard part of a bug report was never the screenshot. It was writing down what you expected, what happened instead, and where you were when it happened, for every bug, one at a time. So most bugs never got written down.
A walkthrough flips that. You look at the app and talk. Toado does the writing. Five minutes of clicking around and complaining turns into five or six tickets that each carry enough context for an agent to go fix them.
How it works
Record → Pin → Tickets → Claude Code → Done.
Point and talk.
Walk through the app like you would with a teammate. When you see something wrong, drop a pin on it (Alt+C) and say what you see. The pin grabs a screenshot and the exact element under your cursor.
Stop. Toado writes the tickets.
Your narration is transcribed and split by pin. Each pin becomes its own ticket: screenshot, element, the words you said at that moment, and a clip of the screen if you recorded it.
Your agent picks them up.
Tickets land on the board. Claude Code, Cursor, or any MCP client reads the transcript, pulls the screenshot and clip, writes the fix, and moves the ticket to In Review.
One pin, one ticket
What every ticket comes with.
Pins are captured through the browser, separate from the recording, so the screenshot and element are full quality in either mode.
Screenshot
A full screenshot of the page at the moment you pinned, captured through the browser, not the video.
The element
The exact DOM element you pointed at, anchored so it can be found again after the page changes.
Your words
The transcript of what you said around that pin. This becomes the ticket description your agent reads.
The clip
In screen-and-narration mode, a short video of the moment. Served to your agent through a one-hour signed URL.
Two modes
Record the screen, or just your voice.
Pick a default in the extension settings. A project can also set the mode for everyone who records in it.
Screen and narration
Records the tab and your voice. Each ticket gets a video clip of the moment you marked. Around 6 MB a minute.
Best for motion bugs: flicker, layout shift, animation, anything you cannot explain in a still.
Narration only
Records your voice. Nothing on screen is recorded. Each ticket still gets its screenshot, the element you pointed at, and what you said. Around 0.5 MB a minute.
Best for copy, spacing, and logic bugs, or when the screen has things on it you do not want stored.
On-page pins
Pins work on their own, too.
Not everything needs a recording. Press Alt+C on any page, click the thing that’s wrong, and a ticket composer opens with the screenshot and the element already attached. Write a line, assign it, done.
- Markers stay on the page. Open tickets show where they are the next time anyone visits.
- Assign as you pin. The composer remembers who you assigned last for the rest of the session.
- Pins mid-recording and pins on their own file the same shape of ticket, so your agent handles both the same way.
For your agent
Built to be read by Claude Code .
A walkthrough ticket is the best bug report an agent can get: the transcript says what
you expected and what you saw, the element says where, and the screenshot and clip
show it. The agent reads all of it with get_ticket and
get_capture_asset over MCP, no copy-paste, no re-explaining.
Retention and privacy
What we keep, and for how long.
Video: 7 days free, 45 days paid
Clips are the expensive part, so they have a shelf life. Free workspaces keep clips for 7 days, Personal and Team keep them for 45. After that the clip is deleted from storage.
Everything else stays with the ticket
The screenshot, the element, the transcript, and the description are kept for as long as the ticket exists, on every plan. The transcript is what your agent reads, so it is never the thing that expires.
Private until it files
A walkthrough in progress is visible only to the person recording it. Nothing is shared with the team until the tickets are created.
Transcription by OpenAI
The audio track is sent to OpenAI for speech-to-text and is not used to train their models under the API terms. Privacy policy and security page have the details.
FAQ
Things people ask about recording.
How long can a walkthrough be?
Up to 30 minutes per recording on a paid plan, and 5 minutes on the free plan. Paid plans also include 600 minutes of recording a month and 300 minutes of transcription; the free plan includes 60 and 30. Most people record for two to five minutes and end up with a handful of tickets.
How long do you keep the video?
Video clips are kept for 7 days on the free tier and 45 days on Personal and Team. After that the clip is deleted. The ticket, its screenshot, the element, and the transcript stay as long as the ticket does.
Do I have to review the tickets before they file?
No. Once processing and transcription finish, Toado files the tickets for you. If the workspace is out of ticket quota, the walkthrough waits in review until you free some up or upgrade.
Who transcribes the audio?
Audio is sent to OpenAI for speech-to-text. Under OpenAI’s API terms it is not used to train models. The full disclosure is in the privacy policy.
Can I use pins without recording?
Yes. Alt+C on any page places a pin and opens a ticket composer with the screenshot and element already attached. Markers stay on the page so you and your team can see which tickets are open where.
Which browsers?
Chrome. Recording uses the Chrome extension on any site you can open, including localhost and staging.
Record your first walkthrough.
Install the extension, open the app you are working on, press Record, and complain out loud. The tickets will be waiting.