Annotate the Still

Once a window (or a Live page) is frozen, you’re in the annotation editor. Everything here is about saying what’s wrong, where — fast.

Marks: pins and regions

• Click the still to drop a pin on a precise spot — a misaligned icon, a stray pixel.
• Drag to draw a region around an area — a whole card, a section with the wrong spacing.

Each mark becomes a numbered sub-issue in the panel docked beside the still, with its own note field. Write each note the way you’d describe the bug to a teammate — your notes are exactly what the agent reads.

The body note

The “What’s the nit?” field at the top holds a note about the capture as a whole — “this whole screen feels cramped”, “dark mode colors are off everywhere”. A capture can be just a body note, just marks, or both.

One note, several places

Sometimes one problem lives in several places — the same misaligned label on three cards. Instead of writing the note three times, select the sub-issue and use + Add place to attach more pins or regions to it. A single-anchor sub-issue badges plainly (2); a multi-anchor one badges its places with letters (2a, 2b, 2c).

Referencing marks in text

Type #2 in any note to refer to sub-issue 2, or #2a to point at one specific place of a multi-anchor sub-issue. Hovering a reference flashes the mark it points to — handy for notes like “make #3 match #1”.

Tags

Add #word tags anywhere in a note or the body — #ios, #dark-mode, #checkout. Tags autocomplete against the project’s existing tags, cross-cut the backlog, and can be used to filter what an agent works on (“fix the #ios issues”). See The nitpin Skill.

Reference images

Paste an image (⌘V) into the body or any note to attach it inline — a mockup, the desired end state, an example to match. It shows as a pill in the text and rides along with the issue; agents view it as part of the intent, right at the point in the note where you pasted it.

Redaction

Sensitive content on screen? Mark a region as redacted and it’s pixelated before the capture is saved — the sensitive pixels never reach disk.

Keyboard

What gets saved

Saving writes one issue to the active project: your sub-issues and body, a clean screenshot, an annotated render with the badges drawn on, and any pasted images. The issue is titled automatically on-device from your text (3–5 words, text-only — the screenshot is never sent anywhere). The title is just a label; your notes are authoritative, and once saved they’re immutable — agents can comment, but never edit your words.