Collaborating with Annotations
Share annotations with teammates who don't have the same dev setup.
Send a review to anyone
For a reviewer handing feedback to a developer, the simplest path is a self-contained export:
- A reviewer annotates the site (staging, production, or localhost)
- They open View All → Share / Export and choose
.html— a single file with every screenshot and reference image embedded - They send it (Slack, email, etc.); the recipient opens it in any browser, no extension required
- The developer works through it and passes the changes to their coding agent
See Sharing exports for the difference between .md and .html.
Round-trip onto a teammate's localhost
To rehydrate live annotations — badges, style previews, and all — onto another machine:
- The reviewer opens View All → Share / Export and chooses
.json - They send the file
- The developer opens Import from the settings menu and selects it — the annotations reappear on their localhost
When importing annotations captured on a public URL into localhost, the extension offers to remap URLs automatically so they anchor to your local dev server.
Important: Annotations might not perfectly anchor if the DOM structure differs between environments. For best results, import into an environment with the same markup.