Most feedback tools make you leave the page first. Amarker doesn't.
Click any element on any page and write your feedback there. Amarker attaches the CSS selector, the page location, and the original HTML — so what your team notices becomes something Claude Code or Cursor can actually act on.
This tool grew out of a real team's feedback problem — read how it started
says nothing
spacing
need this?
A screenshot tells AI something is wrong. Amarker tells it which element to change.
Feedback that arrives as a blurry screenshot turns into guesswork for whoever implements it. Element-level notes keep the location, the structure, and the intent in one place, so the change lands where it should.
Point, don't describe
Every note binds to a real DOM element, capturing its selector, visible text, and surrounding structure.
Never leave the page
Write notes right where you are. Mark up a dozen things in one pass without switching tools.
One shared context
Notes sync across the workspace, and the dashboard keeps open and resolved apart — fewer "is this done yet?" pings.
From review to fix in three steps.
Not another screenshot tool — the layer that carries web feedback into an AI coding workflow.
Open the page
Launch "Page notes" from the side panel and keep the page and its feedback side by side.
Pick an element and comment
Hover to highlight, click to capture. Buttons, headings, cards, and form fields all resolve cleanly.
Copy it to your AI
Paste the structured notes into Claude Code, Cursor, or whichever assistant writes the fix.
Turn "look at this bit" into "change this element."
In early access — a good fit for teams already iterating on pages with AI coding tools.