A step-by-step: turn on Review for a private link, let anyone pin comments to the exact spot (no account), then export the thread as a prompt to paste into Claude or Codex.
You've shared an AI-built page and you want notes on it — specific, in-context notes, not a vague paragraph in a chat. Here's the whole flow, start to finish, on a private link.
On your dashboard, open the document's ⋯ menu and toggle Review on. Nothing about the link changes — it's the same private, unguessable URL you'd share anyway. Review just turns on a comment layer that sits on top of the page.
Leave it off and the page is a clean read; turn it on only for the pages you actually want notes on.
Send the link the way you already do — email, chat, wherever. The reviewer doesn't need a miinideck account, doesn't install anything, and doesn't see your dashboard. They just get a page they can open on any device.
When the page has Review on, a small Review button sits in the corner. The reviewer clicks it, then clicks the exact spot on the page that needs a change, and types a note. They add a name (no sign-up) and the note sticks to that point — and to the screen size they were looking at, so a comment left on the mobile layout doesn't drift onto the desktop one.
Because there's no account wall, the people you sent the link to actually leave notes on the page, instead of replying in chat with "the second card feels heavy."
Open the review workspace and every note is a numbered pin next to the page, with the comments listed in a panel. As the owner you can mark a note resolved once you've handled it — it greys out and strikes through, so a long thread stays readable and you can see at a glance what's left.
Reviewers see each other's pins (like a shared proofing surface), so two people don't leave the same note twice.
Drop a sample page, turn Review on, and leave yourself a pin — see exactly what a reviewer experiences before you send the real link. Free, no card.
When you're ready to iterate, click Export. The whole thread comes out as a clean markdown brief: each note, the element it points at, and the layout it was on — grouped so it reads as a to-do list, not a transcript. (Exporting is the Studio piece; enabling Review and collecting the comments is free.)
Drop the brief into Claude or Codex and say "apply these." Because each note carries its anchor, the model gets the same precision the reviewer had — no retyping, no re-describing "which header." That's the round closed: a reaction on the page becomes a change in the next version, in one move.
To re-prompt cleanly, it helps to have generated portable HTML in the first place — the cross-tool prompt patterns cover what to ask for so the page stays easy to edit and re-share.
This works on pages miinideck hosts — a self-contained HTML file or a zipped build. If what you're building needs a live backend (a server, a database, auth), that's a job for a real deploy platform like Vercel or Netlify; pinned review is for the front-end pages you share as a private link.
The reason to capture feedback on the page instead of in a message is precision: the note never has to be re-mapped onto an element later, and it survives all the way into your next prompt. The mechanics are six steps; the why behind it is one idea — hosting was step one, and this is the step that was missing.
You shared the AI-built page — then what? The real work is the loop: build, show, react, fold the reaction back into the next prompt. Why hosting is only step one, and what actually closes the loop.
The iteration loop with Claude / Cursor / Lovable produces a new version every round. Channels that let each round travel cleanly — without exposing the chat, the previous version, or the next reviewer to noise.
"It asks me to log in." "It's blank." The link isn't broken — it was never built to leave the tool. What each AI tool actually hands you, and what opens.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.