Built with AI
How to let a client edit a site you built with Codex
Codex works on your repository: in the terminal, in your editor, or in the cloud, where it commits or opens a pull request. Connect that same GitHub repository to Siteshare and invite your client. They edit the real site at /edit by chatting, selecting or typing on the page, and publish as one commit on main. Codex keeps working next to them.
- 01
Keep the site in a GitHub repository
Codex cloud tasks work on GitHub repositories you choose. Use the same repository for Siteshare.
- 02
Connect the repository
In the site's folder, run npx siteshare connect, or open Add a site in Siteshare and install the GitHub App on that repository.
- 03
Invite your client
Invite them with their email address and choose their level: Text and images, Blocks and pages, Design or Everything. Anything above it waits for your approval.
- 04
Let Codex and your client work side by side
Codex opens pull requests for you to review. Your client's drafts live on Siteshare's own branch, and only Publish writes to main.
An agent for you, an editor for your client
Codex is built for the person who writes the code: it reads the repository, runs commands and proposes changes for review. Your client needs something else: their own site in front of them, a way to say what should change, and the safety that nothing goes live until it builds.
Siteshare is that second part. It needs no change to your code and no CMS: the assistant edits the files where the content actually is.
Questions
Can my client use Codex instead?
Codex comes with a ChatGPT plan, and it works on code: a terminal, an editor or pull requests. Your client would see code, not their site, and nothing would check a change before it goes live. Siteshare shows them the real site, with drafts and a build check.
Will Codex and my client get in each other's way?
Not more than two colleagues would. A client's published change is a commit on main, and Codex's next pull request starts from there. When your change and the client's draft touch the same lines, the client chooses which one stays, and you hear which.
Which hosts work?
Any host that publishes from main. Tested on Cloudflare, Netlify and Vercel. On Vercel, turn off previews of the draft branch in vercel.json. On a private repository in a GitHub organization, Netlify and Vercel may hold back commits by an author outside your team there, so allow the commits Siteshare makes.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.