What is QA Note? — QA Note Docs

Introducing QA Note

QA Note is the maintenance record & report system at the client boundary. It takes client requests and internal findings in as issues, hands them off to your developer's AI coding agent, has a human verify the fix, and publishes monthly maintenance reports. The fix is executed by the tools you already use (Claude Code, Cursor, etc.) — QA Note keeps the entire process on record.

The record loop

Intake — Capture right on the site with the Chrome extension. Screenshots, console logs, network requests, and environment info are collected automatically, turning every issue into a work order an agent can act on. Client contacts report via magic link, no account needed.
Handoff — Send an issue to a coding agent via the MCP server or the copy-prompt button, and progress is recorded automatically. Even without an agent, an issue key in the commit message records the fix submission.
Verify — Deploy-confirmed issues surface as "ready to verify," and only humans can mark them verified. Issue state model
Report — Publish weekly/monthly maintenance reports. Published reports never change, making them the basis for billing and client reporting.

Key features

Screenshot & Annotation — Capture the screen and pinpoint issues with 10 tools including arrows, boxes, numbered markers, and blur. Learn more
Session Replay — Record the reproduction flow so developers see the exact context. Supports up to 60s manual recording plus instant replay that keeps the last 2 minutes.
Automatic metadata capture — Console logs, network requests/responses, JS errors, Web Vitals, and React component trees are captured automatically.
Maintenance Reports — Publish plain-language summaries per issue with resolution timelines and commit links. Immutable after publish; corrections ship as new versions. Learn more
Commit Key Integration — Issue keys in commit messages (QANOTE-12) record fix submissions automatically; deploy confirmation surfaces "ready to verify." Learn more
MCP Handoff — One issue link delivers screenshots, console, network, and repro steps to your agent. MCP server guide
GitHub bidirectional sync — Issues, statuses, comments, and labels sync with GitHub in real time. GitHub Projects v2 supported.
Slack notifications — Key events like new issues, status changes, and comments are delivered to Slack channels.

Who is it for?

Role	How they use it
Agency owner / Lead	Uses published maintenance reports as billing evidence and contract renewal material.
PM / Verifier	Organizes intake and verifies deploy-confirmed issues, confirming "verified."
Developer	Receives issues via MCP in their own tools and leaves records with just a commit key.
Client contact	Reports via magic link without an account and tracks the progress of their issues.

Introducing QA Note

The record loop

Intake — Capture right on the site with the Chrome extension. Screenshots, console logs, network requests, and environment info are collected automatically, turning every issue into a work order an agent can act on. Client contacts report via magic link, no account needed.

Handoff — Send an issue to a coding agent via the MCP server or the copy-prompt button, and progress is recorded automatically. Even without an agent, an issue key in the commit message records the fix submission.

Verify — Deploy-confirmed issues surface as "ready to verify," and only humans can mark them verified. Issue state model

Report — Publish weekly/monthly maintenance reports. Published reports never change, making them the basis for billing and client reporting.

Key features

Screenshot & Annotation — Capture the screen and pinpoint issues with 10 tools including arrows, boxes, numbered markers, and blur. Learn more

Session Replay — Record the reproduction flow so developers see the exact context. Supports up to 60s manual recording plus instant replay that keeps the last 2 minutes.

Automatic metadata capture — Console logs, network requests/responses, JS errors, Web Vitals, and React component trees are captured automatically.

Maintenance Reports — Publish plain-language summaries per issue with resolution timelines and commit links. Immutable after publish; corrections ship as new versions. Learn more

Commit Key Integration — Issue keys in commit messages (QANOTE-12) record fix submissions automatically; deploy confirmation surfaces "ready to verify." Learn more

MCP Handoff — One issue link delivers screenshots, console, network, and repro steps to your agent. MCP server guide

GitHub bidirectional sync — Issues, statuses, comments, and labels sync with GitHub in real time. GitHub Projects v2 supported.

Slack notifications — Key events like new issues, status changes, and comments are delivered to Slack channels.

Who is it for?

Role	How they use it
Agency owner / Lead	Uses published maintenance reports as billing evidence and contract renewal material.
PM / Verifier	Organizes intake and verifies deploy-confirmed issues, confirming "verified."
Developer	Receives issues via MCP in their own tools and leaves records with just a commit key.
Client contact	Reports via magic link without an account and tracks the progress of their issues.