Pins, comments, and colors

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.

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.

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.

Each element pin also stores a snapshot of what it points at: the element’s HTML tree, the computed styles that differ from the browser defaults, the fonts and icons it uses, and its parent and siblings. The Preview renders the locators and the evidence stored with the pin, while the full snapshot stays in the stored capture and the complete handoff payload. Large elements are trimmed to stay within the capture limit, and the session Markdown says so with a truncated node count.

“Technical evidence” lists facts the extension observed on the page while you pinned: console errors, failed requests, and the environment (browser, viewport, language). Each item is graded “After interaction” when it happened after your last click or keystroke, or “Same page” when it only shares the page. Nothing is inferred and no AI credit is spent; remove an item before sharing if it is unrelated.

• Area pins have no element structure; use an element pin when the agent needs DOM context and resilient locators.
• The default compact prompt keeps the locators, comment, and compact evidence, while the element snapshot travels with the pinar-visual-context block of the complete payload and the session Markdown behind the full-context link.

The pin discussion in the viewer offers the original note and the stored thread comments for editing. The rules differ between the local workspace and Pinar Cloud.

The local workspace has no login, so any note and stored comment can be edited from the viewer. In Pinar Cloud the session owner edits the note, and a human comment is editable only by the person who wrote it. Agent comments are never editable from the viewer.

• An edit saves over the stored text and keeps the message’s identity, authorship, and timestamp.