AgentRegions

Publish a static site from Codex

Use your own Codex CLI and an AgentRegions account to publish files, update the same HTTPS address, and restore an earlier version. AgentRegions manages the private source repository. You can use a managed project without a GitHub account.

Pilot enrollment is closed. On the live test service, two invited accounts verified sign-in, and the publishing account updated and rolled back a public site at the same HTTPS address. Follow this guide if you already have test access, or try the interactive sample.

Connect AgentRegions MCP

Save the AgentRegions connection settings from your invitation in your Codex CLI profile. If the settings use the mcp-remote bridge, start Codex with that profile and ask it to list your AgentRegions projects. Complete sign-in in the browser on the same computer.

If the invitation uses a direct MCP connection, run this command in the same profile and complete browser sign-in.

codex mcp login agentregions --scopes mcp:access

Ask Codex to list your AgentRegions projects to verify the connection. A new account can return an empty list.

If your invitation uses a temporary password, choose a new password when the AgentRegions sign-in page asks. Keep passwords on that sign-in page.

Publish the two-file sample

Download the sample ZIP and unzip it into a new folder. You can also save index.html and styles.css together. Open the folder containing both files in Codex and send this prompt.

Use AgentRegions to publish only the sample index.html and styles.css in this folder as a public site. Use a managed project named birchfold-preview. If it already holds another site, ask me before changing it. Give me the HTTPS link once the deployment reports published.

Open the HTTPS link and check that the page shows “Print worth keeping.” with its stylesheet.

Update the same link

Update birchfold-preview in AgentRegions. Change the headline to “Small runs, lasting impressions.” Keep the stylesheet, publish the change and verify the heading at the existing HTTPS address.

Open the original link to check the new heading.

Give a client a copy of an earlier version

After publishing the headline update, use this prompt while that version is still live.

Find the first published deployment of birchfold-preview in AgentRegions. Export its source revision and save the exact files in a new local folder named birchfold-first-release, preserving their paths. If that folder already exists, ask me before changing it. Leave the current site published.

Open the saved index.html with styles.css beside it. The copy should say “Print worth keeping.” with its styling, and the original HTTPS link should still say “Small runs, lasting impressions.” Share both files together so the recipient can open the same copy.

Restore the first release

Use this prompt when you want the original page back at the public link.

Roll back birchfold-preview to its first published version. Verify that the same HTTPS link shows “Print worth keeping.”

Continue after a disconnect

Open Codex again with the invited account. Ask it to find birchfold-preview and check its deployment history for the intended version. Use the existing deployment when you find it. If the project is missing, check which AgentRegions account is signed in before creating another project.

If there is no deployment, ask Codex to read the latest saved files. Publish that revision if the files match the intended version. If the project has no saved files, ask Codex to save the approved files in that project and publish them. Review any different files before changing the project.

Check what fits the pilot

Choose the finished site folder with index.html at the root. Store assets as regular files. If you ran a build, choose its output folder, such as dist/. Check the folder on your device before publishing. The pilot accepts up to 32 files, 256 KiB per file, and 512 KiB total. It hosts files that work without a server process or database.

When you adapt the sample prompt, name the exact folder you approve for public hosting. The published files are public. The project's source history and export require the project owner's account.