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. Revdoku opens browser sign-in before storing the project.

Just ask to “publish to Revdoku” to publish your as a fast and secure website

from your Codex, Claude or another AI apppublish files or folders

Paste this into your AI app.

Free · Public or protected · Visitor analytics · Forms and email alerts Building websites for clients? Explore Revdoku for agencies

Fastest path: sign in, preview, then publish

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 preview <folder>.
  3. Complete browser sign-in, creating a Free account there if needed.
  4. Review the returned temporary preview URL.
  5. Ask Codex to run revdoku p <folder> when you want the main site live.
  6. Ask Codex for a change, then publish the same folder again. Revdoku updates the same website URL.

The authenticated preview is noindex, lasts 15 minutes, and does not change the main website or consume a live-site slot.

A useful first prompt is:

Build a responsive one-page project website in a new folder. Save it to Revdoku as a private draft, create a temporary preview, and return the preview URL. After I approve it, publish the main website. Remember the Revdoku 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 sign-in, Codex can continue publishing to the same website. Read current Free limits from Revdoku pricing rather than copied limits.

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

Markdown version
↧
Loading PDF…