Point at the element instead of describing it
The slow part of asking an AI to change a page is saying where: the third card, no, the one under the chart, the button that says Submit. On a page hosted at reshare.one you skip that. Hold ⌘, click the element, write the note. Your assistant reads every note with the exact CSS selector attached, so "make this bigger" points at one element instead of a guess.
Here is the loop end to end: what you do on the page, what the assistant sees, and why the link you already shared never changes.
Drop your HTML file
Free.
No copy-paste needed
Add the reshare connector to Claude once, then publishing is one sentence in the chat.
How it works
- 01
Connect your assistant
Add reshare as a connection in Claude, Claude Code, or Codex: paste one address, sign in, approve. About a minute, once.
- 02
Leave notes on the live page
Turn on comments for the file, open its link, and work through it with ⌘ held: this heading shorter, this chart taller, this button blue. Each note pins to the element you clicked.
- 03
Say "read my comments and fix them"
The assistant lists your notes, pulls the page’s source, makes the edits, publishes the new version to the same link, and resolves the notes it handled. Reload the page and the bubbles are gone.
What the assistant actually sees
Your note arrives as two parts: the text you wrote and the selector of the element you clicked, like #pricing or body > section:nth-of-type(2) > h2. The text says what to change, the selector says exactly where. The assistant matches the selector against the file’s source and edits that element, not one that merely looks similar.
The tools behind this are plain: one lists your comments, one fetches the file’s real source, one publishes the new version, one resolves a note. Any assistant that supports connections gets all four.
Why this beats pasting a screenshot
A screenshot asks the model to find the element by appearance, and pages are full of elements that look alike. A selector is an address: nothing to find, nothing to confuse. That matters most on pages with repeated cards, rows, and buttons.
Notes also survive the conversation. They wait on the file until resolved, so you can annotate at night and have the assistant work through the list in the morning, in a fresh chat.
The link never changes
Edits publish as a new version of the same file, so the URL you already sent keeps working and simply shows the result. Version history keeps every earlier state, and you can roll back from the dashboard.
Viewers never see any of the machinery. Notes and bubbles render only for you; everyone else gets the plain page before, during, and after.