Dev only · Local only · No account
Point at what's wrong. Your agent fixes it.
Your agent builds a page. You open it, click the headline, and type “this promise is vague.” The comment lands in a file your agent reads — with the route, the component and the exact text you pointed at. It makes the change, and the pin disappears on its own.
The only checkout that pays for itself
Drop in three lines and start collecting payments in minutes. Trusted by teams who care about conversion.
The loop
Three moves, then it's the agent's problem.
- 1
Point
Press T and click anything on your running app — a heading, a button, a field. The element lights up and a numbered pin sticks to its corner.
- 2
Say what's wrong
Type the note the way you'd say it out loud. “This promise is vague.” “Make this field optional.” No ticket, no template.
- 3
Hand it over
Your agent reads the file, finds the code from the route, the component and the text you pointed at, makes the change, and marks it done.
The hand-off
Data, not a protocol.
Comments are a gitignored JSON file and a short section in your AGENTS.md. Any agent that can read a file can pick up a review — Claude Code, Cursor, Aider, whatever you run next year. There is no server to register and no MCP to configure.
Say “pick up the review”, or hit Copy for agent in the panel.
### c_xeogb96781
Tighten this to one sentence.
- route: /
- element: <h3> "A human reviews"
- component: CardContent < Card < Home
- selector: body > div:nth-of-type(1) > div > h3
# when it's done
$ npx webmark resolve c_xeogb96781 --note "shortened"Lifecycle
Comments clean up after themselves.
A comment survives a reload only while it is unresolved and the thing it points at still renders the same text.
Change the copy, delete the component, move it to another page — the comment goes with it. So as your agent works through your feedback, the pins vanish one by one while you watch. Nothing to tick off, no stale annotations piling up.
Resolved ones surface once as an addressed strip carrying your agent's notes, then drop for good.
Is it safe to leave installed?
Development only
The widget and its store both sit behind NODE_ENV === "development". Neither exists in a production build, and CI fails the commit if the widget so much as appears in the bundle.
Local only
The store binds to 127.0.0.1, accepts requests from localhost pages only, and writes one gitignored file inside your project. No account, no telemetry, no service.
Out of your way
It mounts in a shadow root with its own overlay, so it cannot inherit your styles, re-render with your app, or swallow a click meant for your page.
Stop describing the bug. Point at it.
Requires Next.js 15.3+ (App Router) and Node 20+. Uninstall with npx webmark eject — the diff is empty.