Product demo One issue, end to end

Capture the screen.
Understand the problem.

Capture the screen and error context with our Chrome extension. AI explains the evidence, so your team can start from a clear issue.

Start for free Try the workflow

Screen, console and network → AI explanation → team handoff

Jihye opens the QA Note Chrome extension, captures the error area and annotates it. The screenshot, console errors and failed request are collected together. AI distinguishes the observed 401 response from a possible refresh-order cause. Jihye reviews the explanation and files QANOTE-42. Minsu’s local agent reads the evidence over MCP and submits a fix. Seoyeon checks the result and marks it verified.

CHROME EXTENSIONCapture right where the problem happensTurn captured evidence into understanding

demo.local/checkout/complete

DEMO STORE CHECKOUT

Order confirmedPayment completeORDER 1042 · ₩48,000View order

Session refresh failedRedirected to login after checkout01

TCapture area

Context captured with the screen

Screenshot + annotationMarked problem · original preserved01

3 console errorsSessionRefreshError03

POST /auth/refreshFailed network request401

Context · checkout → redirected to login

Chrome extension

Capture more than pixelsKeep annotations, console errors and requests together with the screen.

AIAI explains the issueDraft for review

Observed

Checkout redirected to login. The refresh request returned 401.

Evidence · /auth/refresh · 401

Possible cause

Navigation may have happened before refresh finished.

Check · refresh and navigation order

Review the explanation before filing.Review & file issue

Chrome extensionStart capture

Jihye · QA

Screenshot · annotation · console · network → a clear issue

demo.local/checkout/complete

Order confirmationPayment completeView order

401 · Refresh failedSign in again1

File as issue2 screenshots3 console logs1 request

QANOTE-42

OpenIn progressFix submittedVerified

Session expires right after checkout and returns to the login screen

JHReported JihyeMSAssignee Minsu

2 screenshots3 console logs1 requestActivityFix submitted · commit 8f31c2aVerified by SeoyeonMark verified

Minsu's local coding agentCodex · Claude · MCPWorking

Read QANOTE-42 + evidenceRepro: refresh order errorFix order + regression test8f31c2a · fix submitted

Fix submitted · 8f31c2a

Jihye · QA

Seoyeon · PM

Capture, understand, resolve · 20 secondsExample with a virtual team and synthetic data.

Jihye opens the QA Note Chrome extension, captures the error area and annotates it. The screenshot, console errors and failed request are collected together. AI distinguishes the observed 401 response from a possible refresh-order cause. Jihye reviews the explanation and files QANOTE-42. Minsu’s local agent reads the evidence over MCP and submits a fix. Seoyeon checks the result and marks it verified.

CHROME EXTENSIONCapture right where the problem happensTurn captured evidence into understanding

demo.local/checkout/complete

DEMO STORE CHECKOUT

Order confirmedPayment completeORDER 1042 · ₩48,000View order

Session refresh failedRedirected to login after checkout01

TCapture area

Context captured with the screen

Screenshot + annotationMarked problem · original preserved01

3 console errorsSessionRefreshError03

POST /auth/refreshFailed network request401

Context · checkout → redirected to login

Chrome extension

Capture more than pixelsKeep annotations, console errors and requests together with the screen.

AIAI explains the issueDraft for review

Observed

Payment completed, but the page redirected to login. The session refresh request returned 401.

Evidence · /auth/refresh · 401

Possible cause

The page may have navigated before the session finished refreshing.

Check · refresh and navigation order

Review the explanation before filing.Review & file issue

Chrome extensionStart capture

Jihye · QA

Screenshot · annotation · console · network → a clear issue

01 / 06Capture right where the problem happens02 / 06Turn captured evidence into understanding03 / 06All the evidence. One shared issue.04 / 06Your local agent works in your repo05 / 06The commit returns to the same issue06 / 06A person makes the final call

demo.local/checkout/complete

Order confirmationPayment completeView order

401 · Refresh failedSign in again1

Seoyeon · recheckingRecheck checkoutSession active · no errors

QA NoteCaptured

Evidence

2 screenshots3 console logs1 request

AI suggestionsSession expires after checkoutLikely cause · refresh order2 repro steps drafted3 console · 1 network linked

File as issueFiled

Issue boardQANOTE

Open

In progress

Fix submitted

Verified

QANOTE-42OpenIn progressFix submittedVerifiedSession expires after checkout231JHMSAssignee Minsu8f31c2aMark verifiedSeoyeon

minsu@dev — claude

Working

qanote · issue QANOTE-42 · 3 evidence items readRepro: checkout complete → refresh order bugFix: reorder refresh · add regression testTests pass · commit 8f31c2aqanote · recorded as fix submitted

checkout/session.ts− redirectBeforeRefresh()+ await refreshSession()+ return checkoutSuccess()

Minsu’s local environment

Fix submitted · 8f31c2a

Jihye · QA

Seoyeon · PM

Capture, understand, resolve · 20 secondsExample with a virtual team and synthetic data.

Capture

Keep the description short.
Bring the context with it.

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?"

A plain issueLogged out after payingAfter the payment went through I was logged out. It happens again when I retry.Title · body

A QA Note issueSession expires right after checkout and sends the user back to the login screen

Region screenshots + annotations2 shots · 1 note

Console logs · JS errorsTypeError ×3

Network (13 sensitive headers masked)401 /session/refresh

EnvironmentChrome 127 · macOS · 1512×982

Session replay (up to 60s)42s

User action timeline6 steps

React component treeCheckoutComplete

Core Web VitalsLCP 2.1s · CLS 0.02

Handoff · HANDOFF

In the tool
you already use.

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.

claude · qanote-web

qanote.app/i/ab3c-42 — take care of this issue
resolve_by_url issue summary · 3 console entries · tech context loaded

get_screenshots 2 shots · note "Bounced to this screen after payment" claim_issue work started — recorded on the issue

git commit -m "fix: handle session expiry (QANOTE-42)"
commit key found Fix Submitted recorded · ready to verify once the deploy is confirmed

QANOTE-42 → Fix Submitted · recorded on the issue automatically

PathWhat gets deliveredAutomatic record

1

Copy the contextNo setup · one button

Errors, console, network, environment and screenshot URLs as one markdown block. For any agent.None — the commit key keeps the record

2

Issue URL + MCPConnect MCP once

Summary plus tech context right away. The agent pulls logs and screenshots on demand.Start · finish · comments

3

Commit keyGitHub integration

Not a handoff — a record pathQANOTE-42 alone flips the issue to Fix Submitted

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

Collaborate and verify

See who owns it
and what needs review.

Agent fix submission and human verification stay separate. Only issues with a confirmed deployment can be reviewed, keeping the final decision clear.

Drag a card — only cards that are ready to verify get into Verified.

Open2

Session expires right after checkoutQANOTE-42

4 missing image altsQANOTE-44

In Progress1

Offboarded member shown in the assignee listQANOTE-39 · agent started

Blocked1

GitHub assignee not syncedwaiting on a third party

Fix Submitted2

No endpoint to list commentscommit d778bb2cReady to verify · deploy confirmed

Wrong project name in the notification emailwaiting on deploy

Verified1

Infinite scroll stallsSongwook Han · 3 days ago

Closed1

Included in the July report · 18 issuespublished

BoardEvery status,
the same issue.

BoardListSchedule

CollaborationConversation and fixes,
in one place.

SW@Jihye Kim I reproduced it on staging. Could you verify?

ReporterYour client just
opens the invite link.No account, no seat cost.

qanote.app/r/hjw-siteCopy link

Report

The record of fixes
becomes the invoice.

The monthly maintenance report is a by-product of using QA Note. Once published it never changes, and corrections stay as a new version.

Half a day5 minmonth-end report prep

August 2026 maintenance reportPublished · v1Share linkPDF

Verified31

Fix Submitted → verified, avg.2d

Closed18

QANOTE-42Session expires right after checkoutd778bb2cVerified

QANOTE-39Offboarded member shown in the assignee list3f1a9c0eVerified

QANOTE-31Infinite scroll stalls9b02e7d1Verified

Immutable after publishing · corrections go out as a new version (v2) · the share link opens without an account

Try it yourself

Step through one issue at your own pace

Move through the five stages from report to human verification and see what gets recorded on each screen.

Example team workflowCondensed demo

Report the issue

Jihye annotates the error and files it with the captured evidence.

Example shown with a fictional team and synthetic data.

Ready to filebugQANOTE-42

Session expires right after checkout and sends the user back to the login screen

JHReported by Jihye Kim · Captured by the extension · Just now

Exploring the demo pauses automatic playback.

Discovery

While you browse,
candidates pile up.

Beta

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.

What it does not doIt is not a crawler — only the screens you visit in the current tabIt does not click links, submit forms, buy or delete on your behalfIt does not promise full coverage or continuous monitoring — the range it could not check is shown tooIt does not create issues on its own — only the candidates a person picks

Quick QAChecks one screen in the current tab.About 15s · 13 checks

Companion checkFollows the screens you move through and collects candidates.Same origin · up to 25 screens · 30 min

QA inbox5 candidates7 screens checked · 2 screens not checked

4 missing image alts · /productsQuick QA · accessibility

Ignore File as issue

Console error · /checkout/completeCompanion check · screen 5/7

Ignore File as issue

1 broken link · /aboutCompanion check · screen 2/7

Ignore File as issue

Here is what changes, role by role.

Developer · solo maintenance — a bug that will not reproduce

BeforeA round trip that starts with "which browser was it?"

With QA NoteOne issue URL → the agent reads the screenshot and console first, then starts

PM · verifier · 8-person agency — confirming fixes

BeforeClicking through everything again on staging

With QA NoteOnly deploy-confirmed issues get the "ready to verify" badge → check those and mark them Verified

Client-side owner — a checkout error found while reviewing the relaunched site

BeforeScreenshot → messenger → cannot reproduce → a spreadsheet at month end

With QA NoteOne click files a card with the evidence → status lives on the board → at month end you just publish the report

Frequently asked questions

Did not find your answer? Average reply in 2 hours · Korean support

Contact us

Yes. 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.

The system keeps the record,
a person verifies.

Start without a card and go all the way to your first maintenance report.

Start for free Contact sales

Free Solo plan · 2 projects · 3 members · 50 issues/month

See usage limits

Capture the screen.Understand the problem.

Keep the description short.Bring the context with it.

In the toolyou already use.

See who owns itand what needs review.

The record of fixesbecomes the invoice.

Step through one issue at your own pace

Session expires right after checkout and sends the user back to the login screen

While you browse,candidates pile up.

Here is what changes, role by role.

Frequently asked questions

The system keeps the record,a person verifies.

Capture the screen.Understand the problem.

Keep the description short.Bring the context with it.

In the toolyou already use.

See who owns itand what needs review.

The record of fixesbecomes the invoice.

Step through one issue at your own pace

Session expires right after checkout and sends the user back to the login screen

While you browse,candidates pile up.

Here is what changes, role by role.

Frequently asked questions

The system keeps the record,a person verifies.

We do not lock the core away.

Capture the screen.
Understand the problem.

Keep the description short.
Bring the context with it.

In the tool
you already use.

See who owns it
and what needs review.

The record of fixes
becomes the invoice.

While you browse,
candidates pile up.

The system keeps the record,
a person verifies.

Capture the screen.
Understand the problem.

Keep the description short.
Bring the context with it.

In the tool
you already use.

See who owns it
and what needs review.

The record of fixes
becomes the invoice.

While you browse,
candidates pile up.

The system keeps the record,
a person verifies.