Connect Codex
The pilot uses your Codex and an AgentRegions account. Managed projects handle the private source repository for you, so you can publish without a GitHub account.
MCP hosting for static sites
See how the pilot uses Codex CLI for a static client preview or campaign page. Publish it, update it at the same HTTPS address, and export the exact source version you sent for review.
Enrollment is closed.
Try the sample updatehttps://studio.exampleBirchfold Print Studio
Print worth keeping.
An update changes the headline to “Small runs, lasting impressions.” at the same link. A rollback restores “Print worth keeping.” Read the update prompt.
First release files index.html styles.css
The pilot uses your Codex and an AgentRegions account. Managed projects handle the private source repository for you, so you can publish without a GitHub account.
Ask Codex to publish your files. AgentRegions verifies the version at its HTTPS link. The published files are public.
Ask Codex to update the same site, restore an earlier release, or export the files from a chosen version. AgentRegions keeps source history private.
If you work in Codex and have a small static client page to update this week, bring an example edit and the name of your current host. In a 15-minute pilot session, you’ll try a sample page and compare the steps with how you publish today.
Use the finished folder, such as dist/, with index.html at the root. Use regular files. The pilot accepts up to 32 files, 256 KiB per file and 512 KiB total.
Choose the folder you would publish to check its files and the local pages, scripts, styles and images linked from index.html. Your browser may skip symbolic links. The selected files stay on your device.
The Codex workflow passed local testing. We’re preparing live sign-in, billing and recovery checks before inviting participants.