Built this for the gap between “agent shipped a page” and “someone can tell you it feels wrong.”
Your agent shares a page → you send a link → anyone pins notes on their phone with no login → notes come back as markdown the agent can apply. No reviewer account. Remote MCP if you want to stay in the editor.
If you’re shipping a page with Cursor this week: go to Send your page out for review · twocents (MCP is under /mcp on that same site), share a page you’re already building, send the review link to one real person on their phone, see if they pin. Reply here with what happened — even if they bounced.
The useful part to preserve in the markdown is not just the note, but its anchor: a stable selector or DOM fingerprint, the viewport, and a short rendered-text excerpt. Otherwise the page can move between review and apply, and the agent may confidently edit the wrong element; I’d mark unresolved or stale notes explicitly instead of silently remapping them.
You’re right, and before any changes are applied its not just the note but the anchor that are preserved in markdown. After changes are applied there is a potential disconnect, as you described.
Is the history important to you or would simply marking stale/addressed notes as resolved be good enough?
When the underlying anchor has been removed I’m thinking of just moving the addressed comment to a side panel, unattached and marked as addressed.
I’d keep a minimal history: original anchor, note, resolution status, and the change that addressed it. Moving detached comments to a resolved side panel sounds right, but retaining that audit trail helps when a later change reintroduces the issue.