Claude Code client handoff
How to share a Claude Code site with a client
Build the static site, share one controlled review URL, and turn client comments into a precise prompt for the next Claude Code session.
From build to client review
- 1
Create a reviewable production build
Ask Claude Code to run the project tests and documented production build. Review the diff yourself, then identify the generated static output directory.
- 2
Run a client-facing preflight
Serve the output locally and inspect every route at desktop and mobile widths. Confirm that assets, forms, accessibility basics, and external links behave as intended.
- 3
Upload the exact output
Zip the output contents with index.html at the root. Upload the archive and use the resulting manifest-backed version as the review candidate.
- 4
Keep feedback attached to the build
Share the stable preview URL. The client can pin comments to the page while each note remains tied to the immutable version they saw.
- 5
Start the revision with structured context
Generate and review the revision plan, paste the builder prompt into Claude Code, implement and test the changes, then upload the next version to the same project.
Common questions
Does PreviewSend run Claude Code?
No. Claude Code remains your development tool. PreviewSend hosts the compatible static output and structures the client feedback you take back into your coding workflow.
Can the feedback prompt change my code automatically?
No. The generated prompt is an editable handoff. You review it, paste it into your builder, inspect the resulting code, and run your normal tests.
How is final approval tied to the site?
A named approver link records the decision against one version. Eligible plans can download a sign-off PDF containing the version details and content hash when available.