The easiest way to share a prototypeand 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.

Anything you are building. Run the command in a local prototype’s folder and it hosts a copy, no deploy needed. Or paste a published link: Lovable, v0, Figma Make, ChatGPT Sites, Vercel, Netlify, Bolt, Replit, Azure Static Web Apps, or GitLab Pages. Most prototypes work as they are. If yours needs a real backend, or sits behind a company password, hand it to your coding agent and it captures a working copy from your own browser. Record in Chrome or Edge on desktop.

Yes. Claude Code builds it into a working app, then protoproto shares it for feedback, design notes and all.

They hear you walk through it. When they want a turn, they hit React and drive the prototype themselves, their screen and voice captured as they go. Watching needs no account; a reaction or a comment takes a quick sign-in, so feedback arrives with a name.

Reactions: someone driving your prototype and thinking out loud, so you see what they tried, not only what they said. Plus comments on any moment. Both land on the walkthrough, against the screen they were looking at.

Yes. Attach the thinking behind it, whether a doc, your research, or a link. Anyone watching can then ask, and get answers quoted from what you attached, so your reasoning is in the room without you on the call. Add it from the walkthrough, or let your agent pull in what sits behind a login.

Yes. Claude Code, Cursor, Codex, anything that speaks MCP. It reads what people said and tried, turns that into changes in your prototype, and sets up your next recording link. The first run of the command connects this machine.

Anyone with the link, once you publish it. It stays private until then, and you can add a password. Opening it plays your voice and camera back, and the same from anyone who reacted. Deleting the walkthrough is the only way to take it back, so keep it to sample data.