Precise marks on the pixels
Outline the exact region. Each mark carries intent so the agent knows what to change and what to leave alone.
Built for Reviewers
No MCP. No ReviseMy account. Open the secret link, outline regions on the capture, set intent, and approve or request changes — your marks tell the agent what to do next.
Feedback in Slack threads and Figma comments rarely maps back to structured work for an agent. When someone shares a ReviseMy link, you should know exactly how to leave authoritative marks — and how guest suggestions differ.
Open `/r/{token}` from your agent or teammate. Drag a rectangle or click a point, choose must-fix / nice to have / question / keep, and leave a note. Track marks on the board from open → resolved → verified. Approve when it is done, or request changes so the agent opens the next pass.
Outline the exact region. Each mark carries intent so the agent knows what to change and what to leave alone.
Second-opinion and guest notes are suggestions until you accept them. Only you approve, request changes, or verify fixes.
Send a private guest link when another set of eyes helps. Their suggestions stay non-authoritative until the review owner accepts them.
Follow marks from open to verified. Agents can attach before/after evidence when they resolve a mark so you can sign off with proof.
A short path from opening the link to signing off.
Try saying these to your agent after connecting MCP from the homepage.
No. Reviewers only need the secret /r/{token} link. MCP setup is for the person connecting an agent.
Your marks drive the agent’s next_action. Second opinion is optional AI/checklist hints — useful, never decisions.
Yes. Use the guest share link. Suggestions wait for the review owner to accept them into authoritative marks.