Pins, comments, and colors
Use numbered pins as stable references between the screenshot, prose, and structured context.
4 minIn this guide
One shared capture
Every numbered badge on the screenshot maps to one comment and one pin record. The rotating color palette separates nearby markers without changing their identity.
Keep the correlation
Do not rewrite captureId or pinId when handing the bundle to another tool. Those fields let the workspace, viewer, agent result, and review history refer to the same capture.
How numbers and identities are assigned
A pin is saved only after the comment is trimmed and non-empty. New pins receive a UUID, a 1-based number from their order in the capture, and a color from the eleven-swatch palette at that number. Nearby badges therefore differ visually without changing which identity they keep.
Structured context keeps pinId from the existing pinId or id. When those fields are absent, the parser synthesizes captureId:pN from the capture identity and the pin number. Downstream tools can then point at the same screenshot, comment, and review row.
- An empty composer cannot be copied; focus stays on the field until a comment exists.
- Hovering a marker previews its number, comment, and current locator confidence on the live page.
- Editing an existing pin updates only its comment; the stored id is left unchanged.