Skip to content
Toado Docs

Your first capture

You have an account, the extension is installed, you have a project. Time to capture.

The flow in 6 steps

  1. Open any page in Chrome.
  2. Spot something you want to file (a layout bug, a console error, a slow request, anything).
  3. Click the Toado icon in your toolbar (or press Alt + C to capture without the popup).
  4. Toado captures the screenshot, console, network, errors, performance, and URL. The new ticket opens in a new tab.
  5. In the ticket detail page: write a title, optionally annotate the screenshot, optionally add a description.
  6. Done. The ticket is on the To Do column of the project you chose.

What happens behind the scenes

When you click capture, the extension:

  1. Takes a screenshot of the visible viewport (chrome.tabs.captureVisibleTab).
  2. Pulls the in-memory console buffer that the content script has been collecting since the page loaded.
  3. Pulls the network log from the same buffer.
  4. Pulls any uncaught errors and unhandled promise rejections.
  5. Pulls performance metrics (performance.getEntriesByType('navigation'), long tasks, Web Vitals).
  6. Bundles all of it with the URL and a timestamp.
  7. Uploads to Toado over HTTPS (or queues offline if the API is unreachable, see Offline mode).
  8. Opens the new ticket page in a fresh tab.

If any data category fails (e.g., CSP blocks the in-page injection), the ticket lands with a capture health banner explaining what is missing and why. Nothing silently disappears.

Naming the ticket

Toado creates the ticket with a placeholder title (“Untitled capture”). A backend worker then runs an AI title generation pass within a few seconds, so by the time you read the ticket the title usually reads something like “404 on /api/users in checkout flow”.

You can always edit the title manually. The auto-generated title is a starting point, not a lock-in.

Annotating the screenshot

In the ticket detail view, the screenshot has an annotation toolbar above it:

  • Pen for freehand strokes.
  • Highlighter for translucent overlays.
  • Circle for drawing attention to a specific element.
  • Color picker with five preset colors (red, yellow, green, blue, magenta).
  • Redact for blacking out or blurring sensitive regions before sharing.
  • Undo / redo.

Annotations are saved as a separate overlay layer; the underlying screenshot is never modified destructively. See Annotations for the full toolbar reference.

What to do with the ticket

Three common paths from here:

  • Fix it yourself. Open the ticket, read the capture, fix the code, drag to Done.
  • Hand it to Claude Code. Set up the MCP integration, then in Claude Code: “Take the top ticket from To Do in my Acme Web project, fix it, and post a comment with what you did.”
  • Triage with a teammate. Drag to In Progress, assign a teammate (see Roles & permissions), and drop a comment with context.

What is next