Glossary

A short, opinionated glossary. 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 › Main region.

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). Created by clicking the Chrome extension.

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 Capturing › Capture health banner.

Column

A vertical lane on a project’s kanban board. Defaults: To Do, In Progress, Done. Configurable per project. 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.

DevTools panel

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

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 22 tools. See Claude Code › Quickstart.

MCP client

Anything that speaks MCP and has been registered with a Toado MCP token. In practice: Claude Code, Claude Desktop, Cursor, the VS Code Claude Dev extension. 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.

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. For genuine deletion at capture time, use Redact image regions on capture in the extension options.

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.

Scope

A capability a token grants. Four scopes: read, comments, tickets:write, tickets:assign. See Tokens & scopes.

Skill

A prompt template in ~/.claude/skills/<name>/SKILL.md (or project-scoped in .claude/skills/). Invoked with /skill-name. Toado ships several skills (toado-triage, toado-verify, etc.) that wrap MCP tool sequences into one-line calls. See Skills overview.

Source URL

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

Token

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

URL pattern

A wildcard or regex on a project that the Chrome extension uses to auto-pick the project for a capture. See Capturing › Project assignment.

User

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