The easiest way to share a prototype and get feedback you can actually use.

Stakeholders follow your walkthrough, click through the live prototype, and react out loud. And it all lands right in your agent.

npx protoproto share

Run it in your prototype's folder, or hand it to your coding agent.

FAQ

  1. 1Share it. Run the command in your prototype's folder. It hosts a copy and gives you a link to record against.
  2. 2Walk through it. Open that link and talk over your prototype for a minute.
  3. 3Hear back. Send it on. They watch, hit React to take a turn, and their screen and voice are captured while they think out loud.
  4. 4Ship the next one. It lands back in your agent, which turns what they said and did into your next version.

A prototype in a folder on your machine, or one you have published. For a local one, run the command above in its folder: it builds a static copy and hosts it, no deploy needed. For a published one, paste the link you would send a colleague. Lovable, v0, Figma Make, Vercel, Netlify, Bolt, Replit, Azure Static Web Apps and GitLab Pages all work. It needs to open without a login, and you will want Chrome or Edge on desktop to record.

It works on anything that builds to a static site and does not need its own live backend, which is what most prototypes are. React, Vue, Svelte, plain HTML or a framework build are all fine. If yours genuinely needs a running server, the command says so rather than hosting something broken.

They hear you walk through it. When they want a turn, they hit React: your prototype comes up live in front of them, and their screen and voice are captured while they use it. Watching takes no account; leaving a reaction or comment takes a quick sign-in, so the feedback comes with a name. It is your live prototype, so keep it to sample data.

Reactions, which are someone using your prototype and thinking out loud. You see their screen and what they tried, not just what they said. And comments on any moment. Both land on the walkthrough, against the part they were looking at.

Yes. Attach the thinking and evidence behind the work, from a doc or a link to your research and data. Then anyone watching can ask about it and get an answer quoted from what you attached, so your reasoning is in the room without you on a call. Add it from the walkthrough, or have your agent bring in what sits behind a login.

Yes. Claude Code, Cursor, Codex, and anything that speaks MCP can read your walkthroughs, how many watched, what people said and what they tried, turn that into changes in your prototype, and set up your next recording link. The first run of the command above connects this machine.

Anyone with the link, once you have published it, and it stays private until then. You can password-protect the link. Opening it plays the recordings too: your voice, your camera if you used it, and the same from anyone who reacts. Deleting the walkthrough is the only way to take it back. Keep it to sample data all the same.