Publish websites from Codex with Revdoku

Turn a static site built in Codex into a live URL, then update that same URL as the project changes. The quickest first publish does not require an account.

Fastest path: publish before signing up

In Codex CLI or another local Codex session with shell access:

1. Ask Codex to build the site in a folder.
2. Ask it to install the Revdoku client and run revdoku p <folder>.
3. Open the returned public preview URL.
4. Use the claim link within 24 hours if you want to keep the site.
5. Ask Codex for a change, then publish the same folder again. Revdoku updates the same website URL.

The anonymous preview is public, lasts 24 hours, and supports one website up to 25 MB. No signup or credit card is required. Claiming it creates a free account and keeps that same website online permanently.

A useful first prompt is:

Build a responsive one-page project website in a new folder. Publish that folder to Revdoku, return the live URL and claim link, and remember the Revdoku website binding so later changes update the same URL.

Codex CLI and local coding sessions

Local Codex sessions are the best fit when the project includes images, fonts, PDFs, or other binary files because the Revdoku client can upload the folder directly.

If Codex needs explicit instructions, use:

1. Install the current Revdoku skill or client from the instructions copied from Revdoku.
2. Change into the project directory.
3. Run revdoku p for the current folder, or revdoku p path/to/site.
4. Keep the local Revdoku binding file with the project.
5. Run the same publish command after each edit.

Do not create a fresh website for each revision. Reusing the bound folder is what preserves the URL.

After you claim the preview, Codex can continue publishing to the same website. The free account includes 5 GB total storage and up to 100 published websites.

Codex desktop and hosted MCP

Codex can also connect to Revdoku’s hosted MCP server:

codex mcp add revdoku --url https://app.revdoku.com/mcp
codex mcp login revdoku

Complete the OAuth sign-in in your browser, then ask Codex to list the available Revdoku tools. The hosted MCP connection is useful for creating or editing text-based site files and republishing an existing Revdoku website.

For a folder that contains binary assets or exists only on your computer, use the local client instead. A remote MCP server cannot read arbitrary files from your machine.

See the MCP website-publishing guide for client-specific setup and troubleshooting.

Codex inside ChatGPT

When Codex runs inside ChatGPT, use the Revdoku app if it is available in your ChatGPT workspace. Workspace settings can control which apps are enabled. Connect Revdoku, choose the existing website when revising it, and ask Codex to return the published URL.

For a local project folder, Codex CLI remains the direct route because it can access the files on disk.

Verify the same-URL workflow

After the first publish:

1. Copy the website URL.
2. Ask Codex to change one visible heading.
3. Republish the same bound folder or update the same MCP website.
4. Reload the original URL.
5. Confirm the heading changed and the URL did not.

This short test catches the most common mistake: creating a disconnected website instead of updating the original one.

What Revdoku publishes

Revdoku hosts static output: HTML, CSS, JavaScript, images, fonts, documents, and other files. It does not run a server-side application process. If Codex built a framework project, ask it to run the production build first and publish the generated static output directory.

Next steps

• Use Revdoku with OpenClaw.
• Connect any compatible client through the Revdoku MCP server.
• Review the website publishing API.