Glossary

A short, opinionated glossary, in alphabetical order. Definitions are scoped to how Toado uses the term, which is sometimes narrower than the general industry meaning.

Annotation

A vector shape (stroke, circle, arrow, text, redaction) drawn on top of a captured screenshot. Stored as a structured shape with image-pixel coordinates, and rendered as an overlay layer. The underlying screenshot is never modified destructively. See Annotations.

Attachment

An additional image uploaded to a ticket beyond the original capture. Annotatable with the same toolbar. See Ticket detail › Layout.

Bug intake column

An optional per-project column that holds widget and report-link submissions until someone triages them. Off by default; turned on in project settings with Route incoming widget reports to a Bug intake column. Triage happens from the bulk action bar: Move… sends the selected tickets to a working column, Archive drops them. See Board.

An embedded reporting interface installed with a project-specific script. It lets external reporters or team members create context-rich tickets from the page where a problem occurs. See Bug report widget.

Capture

A bundled snapshot of a page at a moment in time: screenshot, console log, network log, errors, performance entries, URL, plus metadata (capture id, timestamp, capture quality flags). Banked at the instant a pin is placed, or taken for the whole page by classic capture.

A non-blocking banner on the ticket detail page that explains what came back partial or empty in a capture (e.g., console blocked by CSP). Surfaces to both human and AI readers so neither debugs from incomplete data without knowing. See Classic capture.

Capture mode

How the evidence on a ticket was gathered, stored as captureMode on the ticket: a page pin (screenshot banked at the click, plus the element), classic capture (the whole visible page plus DevTools state), or a walkthrough clip.

Capture profile

A company-level rule, keyed by URL prefix, that sets what the extension captures on matching sites so each member does not configure it per machine. Three modes: Full capture, Metadata only, Never capture. Managed under Company Settings › Capture profiles. The most specific matching prefix wins. Metadata only withholds screenshot assets and request/response bodies and blocks page pins; Never capture blocks capture entirely.

Clip

The short video cut from a walkthrough recording for one ticket. It plays in the ticket’s image area. Clips have plan-configured retention; check the allowance displayed by the app. The ticket, description, and transcript can outlive the clip. See Walkthrough media retention.

Column

A vertical lane on a project’s kanban board. Defaults: To Do, In Progress, Response Required, In Review, Done. Configurable per project up to 15 columns, plus the optional Bug intake column. See Companies & projects › Column.

Company

The top-level container in Toado’s data model. Contains projects, members, tokens, billing. A user can belong to multiple companies. See Companies & projects.

Deep capture

An opt-in widget level that instruments networking APIs to collect additional redacted request details and status codes. It requires compatibility testing. See Widget capture.

DevTools panel

The four-tab viewer (Console, Network, Errors, Performance) on the ticket detail page that shows the captured DevTools data. See DevTools panel.

Element anchor

The record of which element a pin was placed on: selector, tag, id, classes, test id, aria-label, a redacted text snippet and the component name. Written at capture time. The pins panel uses it to put the marker back on the page, and get_ticket returns it, minus the geometry, as the element block. It is an API field for now; the ticket page does not render it yet. See Tools reference › The element block.

External report

A ticket submitted outside the workspace through a bug report widget or public report link. The board’s From customers quick filter shows only these; the reporter details on them carry an unverified tag because they are self-reported.

In-page logging

The toggle on the extension’s Options page that decides what Alt+C does. On, it arms pin mode; off, it runs classic capture. Fresh installs start with it on; updates from 0.1.x start with it off and show a one-time notice in the popup. See Panel options and settings.

Kanban board

The card-and-column layout that organizes tickets by workflow state. Cards move between columns by drag-and-drop. See Board.

MCP

The Model Context Protocol. An open spec for tool-calling between AI clients (like Claude Code) and external services. Toado ships an MCP server that exposes 34 tools in the reviewed 0.2.0 source; its source is public under the MIT licence at github.com/toado-dev/toado-mcp, and the hosted endpoint runs that code. See Claude Code › Quickstart and Source and self-hosting.

MCP client

Anything that speaks MCP and has been connected to the Toado MCP server, by OAuth or a token. In practice: Claude Code, Claude Desktop, Cursor, Codex. Comments and edits from MCP clients are visually distinct from human comments in the UI.

Member

Someone who belongs to a company. Their role (Owner, Admin, Member, Viewer) governs what they can do. See Roles & permissions.

Page identity

The address a pin was placed on, reduced to its origin plus its path. The query string and the fragment are stripped, so https://shop.test/cart?step=2#totals and https://shop.test/cart are the same page. It is how a ticket is matched back to the page it came from, so markers can be restored on later visits. Stored as pageIdentity, and set only on pins; the full address at capture time is kept separately as the source URL.

Page pins

The 0.2.0 extension’s primary way to file a bug: a marker placed on the element you are looking at, with the screenshot banked at that instant and the element recorded on the ticket. Older material calls this in-page capture. See Extension overview and Your first pin.

One placed marker and the ticket behind it. The style picker offers three: Pin, Bug (one of five icons, picked at random per pin) and Number. Two earlier styles, fly and lily pad, are retired: pins saved with them are still drawn, but you cannot choose them for a new pin. Markers are hidden by default per site; Locate finds one while they are hidden. A click on an element that cannot be tracked anchors the pin to the nearest trackable ancestor.

Pins panel

The panel the toolbar icon opens on the page, headed Pins on this page. Capture, deep network capture, settings, connection status, site claiming and walkthrough recording live here. It folds into a pill reading Page pins when minimized. The toolbar icon’s own tooltip is Open Toado page pins. See Extension overview.

Project

A kanban board scoped to one company. Has a name, optional URL patterns (for extension auto-pick), and a column set. See Companies & projects › Project.

Redaction

Masking part of a captured screenshot before or after upload. Two flavors in the annotation toolbar: opaque (black box) and blur. Annotation-layer redaction is presentation, not deletion: the raw bytes still exist on the server. There is no capture-time image redaction, so deletion of the pixels is not available at any point: if the content must not reach the server, do not capture the page.

Resolved

A boolean flag on a ticket, independent of column. A ticket can be resolved while still on the board; archiving is a separate action.

Response Required

A default column between In Progress and In Review for tickets that an agent or a teammate is blocked on and needs a human answer for. The toado-triage skill moves blocked tickets here instead of leaving them in In Progress. See Board.

Scope

A capability a token grants. Five canonical permissions: mcp.read, mcp.comments, mcp.tickets.write, mcp.tickets.assign, and explicitly opted-in mcp.jira.send. Read accompanies every grant; mutation permissions do not grant one another. See Tokens & scopes.

Site claim

Adding an origin to Toado from the pins panel, on the card headed Add this site to keep pins here (New project for this site, or pick a project and press Add this site here), so pins on it route to a project. An unclaimed origin shows the claim card instead of the panel. See Extension overview.

Skill

A prompt template in ~/.claude/skills/<name>/SKILL.md (or project-scoped in .claude/skills/). Toado ships toado-triage, which wraps the fix, verify and dedupe flows into one skill, plus two smaller variants. See Skills overview.

Source

The source field on every ticket, saying which path filed it: extension, widget, public_link, team_snippet, mcp, manual or recording. Returned by get_ticket and shown as a badge on the ticket: Widget, Report link, Team snippet, AI agent (the mcp source), Manual or Walkthrough (the recording source). Extension captures show no badge.

Source URL

The URL of the page the capture was taken from. Always recorded on a ticket. Click to open in a new tab.

Standard capture

The recommended widget level: DOM-rendered screenshot, page/browser context, console and errors, and passive network resource information without deep networking instrumentation. See Widget capture.

Token

An API token used to authenticate REST or MCP calls. Per-user, scoped, optionally restricted to companies or projects. Created in Company settings > MCP tokens. See API tokens.

URL pattern

A rule on a project that the extension uses to pick the project for a pin or capture. A bare origin means the whole site; the most specific matching pattern wins, and duplicates collapse on save. Your own workspace is searched first, so a project there wins even when another workspace you belong to has a closer pattern for the page. See Companies & projects.

User

The Toado account you sign in with. One email, one user. See Companies & projects › User.

Walkthrough

A narrated recording, with optional screen capture, up to 30 minutes, made from the pins panel or Video walkthrough in the web app. Uploading it produces auto-created tickets, each with a clip, an interpreted description, and the verbatim transcript under a What was said divider, plus any pins placed with Alt+click while recording. See Walkthrough recording.

A public, project-specific identifier in the generated installation snippet. Allowed-site rules and project configuration restrict its use. See Widget security.

Where to next

Extension overview for pins, the panel and classic capture in context.
Tools reference for the fields an agent sees on a ticket.
Board for the columns and filters the terms above refer to.