Features

Comment on the exact element

Select a heading, button, image, or form control and describe what should change. anmerko saves the element type, selector, visible text, accessible label, and viewport size with your note.

• Select Element, then click the target. Use Parent Element steps up to the container when the first pick is too narrow.
• Numbered page markers; Locate scrolls back to the saved target when the page still matches it.
• Edit and delete from the comment card; drafts survive moving between the floating panel and the sidebar.

Inline comments →

Capture a visual region

For feedback about a look or layout, drag a box over the region and comment on the crop. Only the cropped PNG is stored — never the rest of the screen.

• Keyboard support: arrows move, corners resize, Shift steps by ten pixels, Esc cancels.
• Crops are limited to 2,400 pixels on the longest side and about 2 MB each.
• Review each crop before sharing — it includes everything visible in the box.

Screenshot comments →

Screenshot the full page

When the feedback spans a whole layout, choose Full Page instead of dragging a box. anmerko scrolls from the top of the page to the bottom, stitches the screens into one image, and returns you to where you were.

• Fixed and sticky headers appear once, at the top, instead of repeating down the image.
• Long pages are saved as JPEG when a PNG would exceed about 2 MB, so they keep their detail. Pages up to about 65,000 pixels tall fit in one image.
• The prompt marks the image as a full-page capture so your agent reads it as the whole layout.

Full-page screenshots →

Comment on the whole page

Hierarchy, visual direction, overall experience — some feedback is about the page, not one element. Global comments save with the page title and URL.

Global comments →

Optional framework component hints

Off by default. Enable Capture component context in Settings to add a component-name hint (for example, App > PricingPage > PlanCard) to new element comments when the site exposes supported React, Vue, Angular, or Preact metadata.

• At most eight names; a separate hint row, never mixed into the selector or DOM ancestry.
• Saved snapshot: exports reuse what was captured, and never re-inspect the page. Remove a hint while editing if you don't want to share it.
• Honest fallback: production builds and unsupported pages keep ordinary element context with no invented names. Svelte and Solid intentionally receive ordinary context — neither keeps a runtime component tree to read.
• Astro islands report their framework, component export, and hydration strategy; static Astro output carries no names.

Component hints →

Hand your agent a clean brief

Choose This page or All pages, then Copy Prompt for Markdown with your feedback, page URLs, and captured context — or Download Markdown + Images for a ZIP with matching PNGs.

• Customizable prompt preamble under Settings.
• See a real example prompt exported from Salad Recipe Finder.

Send to your agent →