Capture the screen and error context together, then hand it to the coding agent you already use. Fix submission and human verification stay on the same issue.
The system keeps the evidence. A person makes the final call.
Jihye captures the 401 session refresh failure on the checkout screen and files it as issue QANOTE-42. Minsu takes it, and his local coding agent reads the issue and evidence over MCP, fixes it, and records commit 8f31c2a as a fix submission. Seoyeon checks the result and marks it verified.
Capture the screenshot, console, network, and environment together so the next person can start from a useful issue.
An issue with only a title and a body sends you back to asking "which browser was it?"
One issue link and the coding agent you already use reads the screen and the error record first, then starts working. We support this flow officially over MCP — 24 tools. Claude Code · Cursor · Codex · Windsurf.
Sensitive fields are masked before they are delivered · Storage/DOM is opt-in · the agent reads only inside project permissions · commit and deploy records come from supported GitHub · Vercel integrations
Agent fix submission and human verification stay separate. Only issues with a confirmed deployment can be reviewed, keeping the final decision clear.
The monthly maintenance report is a by-product of using QA Note. Once published it never changes, and corrections stay as a new version.
Move through the five stages from report to human verification and see what gets recorded on each screen.
Report the issue
Jihye annotates the error and files it with the captured evidence.
While you browse your own site, QA Note collects problem candidates from the screens you visit, signed in as you. It never clicks or submits forms on your behalf.
Did not find your answer? Average reply in 2 hours · Korean support
Contact usYes. Paste the issue URL and the agent reads the summary, console and screenshots over MCP before it starts. We support 24 tools officially, and you only connect once.
Yes. Put an issue key such as QANOTE-42 in the commit message and the GitHub integration records "Fix Submitted" for you. Capture, board and reports work exactly the same.
Only a person can. An agent goes as far as "Fix Submitted", and the server enforces it with a 403. Only issues with a confirmed deploy are marked "ready to verify".
About 2 minutes. Install the Chrome extension, create a project, and you can file your first issue. No card required.
No. They just open the invite link to report. No account, no seat cost.
A published report never changes. If a correction is needed it goes out as a new version, and the earlier version stays.
Yes. Reporters file in one click from the screen and follow the status on the board. Console and network collection is automatic.
13 kinds of sensitive headers are masked automatically before delivery. Storage/DOM collection is opt-in, and the agent reads only inside project permissions.
The latest Solo usage is shown from the same source in the plan cards and pricing page. It is free forever with no time limit, and the core features are not locked away.
Pro billed yearly is ₩10,200/seat/mo (₩12,000 billed monthly). During the Pilot we handle it as an onboarding conversation.
Start without a card and go all the way to your first maintenance report.