Cursor client handoff
How to share a Cursor project with a client
Build the static output from your Cursor project, share one controlled review URL, and turn client comments into the next Cursor prompt.
From build to client review
- 1
Run the production build
Ask Cursor to run the project's tests and its documented production build, then read the diff yourself before anything goes to a client.
- 2
Find the static output
Locate the output directory and confirm it contains index.html. Open the built files in a clean browser window to catch absolute asset paths.
- 3
Create the review project
Zip the contents of the output directory and upload them. Add a project password if only people with the shared secret should open it. If you work with an MCP client, PreviewSend also has an MCP server that can create a project and deploy a build from your editor.
- 4
Ask for pinned feedback
Send the link with a deadline and ask for comments on the exact elements to change. The client needs no account and no extension.
- 5
Feed the comments back
Turn unresolved comments into one structured prompt for the next Cursor session, then upload the new build to the same project so the client link stays the same.
Common questions
Can I upload my Cursor project folder directly?
Upload the built static output, not source files that still need a bundler or dev server. The archive needs an index.html entry point.
Do clients need to install anything?
No. The review controls load on the hosted preview and reviewers identify themselves with a display name.
What happens to comments when I upload a new build?
Keep every upload in one PreviewSend project. Comments stay tied to the version they were made on while that version is retained, and the client keeps using the same project URL. Older versions are pruned by your plan's version limit, so copy any comments you still need into your next prompt before they age out.