Codex client handoff
How to share a Codex-built site with a client
Build the static site with Codex, share one controlled review URL, and turn client comments into a precise prompt for the next Codex run.
From build to client review
- 1
Have Codex run the build
Ask Codex to run the tests and the documented production build. Review the diff yourself before sharing anything.
- 2
Check the static output
Find the output directory, confirm index.html exists and open the files in a clean browser to catch absolute paths.
- 3
Create the review project
Zip the contents of the output directory and upload them. Add a project password if the preview should be limited. PreviewSend also has an MCP server, so an MCP-capable agent can create a project and deploy a build itself.
- 4
Ask for pinned feedback
Send the link with a deadline and ask the client to comment on the exact elements to change. No account or extension is needed.
- 5
Hand the comments back
Turn unresolved comments into one structured prompt for the next Codex run, then upload the new build to the same project.
Common questions
Can Codex deploy to PreviewSend itself?
PreviewSend has an MCP server with tools to create a project and deploy a build. Whether your Codex setup can call it depends on how you have configured MCP servers.
Do clients need an account to comment?
No. Reviewers need only a display name.
Do comments survive a new upload?
Yes, while that version is retained. Comments stay tied to the version they were made on, older versions are pruned by your plan's version limit, and the project URL stays the same.