Codex can build the page. It can write the code, optimize the assets, and run the tests. Then it stops — publishing requires deployment infrastructure that Codex doesn't include natively.
The last mile of any Codex workflow: how do you get the output to a live URL? Here's how to add deploy and publish capabilities to Codex, from static pages to shareable links to full hosting.
The Codex Publishing Gap
Codex operates in ephemeral cloud sandboxes. It can generate complete, production-ready HTML, CSS, JavaScript, and static assets — but those files live in the sandbox, and the sandbox isn't publicly accessible.
Publishing requires at minimum:
- A publicly accessible URL or hosting environment
- A way to get files from the sandbox to that environment
- Authentication with the hosting provider
None of that is native to Codex. The options differ mainly in how much infrastructure overhead they add.
What Codex + Publish Capability Unlocks
When you add publish capability to Codex, the agent's output becomes shareable immediately:
- Instant review links. Codex generates a landing page mockup, publishes it to a live URL, and returns the link — ready for stakeholder review without any deployment pipeline.
- Generated content pages. Blog posts, documentation pages, changelogs — Codex writes and publishes in one workflow.
- Client deliverables. Generated reports, proposals, visual presentations — published to a URL that clients can open in a browser.
- A/B variants for review. Codex generates two landing page variations, publishes both to separate URLs, and returns both links for comparison.
- Generated media hosting. Images and videos generated by Codex get hosted at permanent URLs, ready to embed in live sites.
Method 1: Deploy to Vercel, Netlify, or Similar Platforms
Codex can install and call deployment CLIs in its sandbox:
# Vercel
npm i -g vercel
vercel deploy --prod
# Netlify
npm i -g netlify-cli
netlify deploy --dir=./dist --prod
Setup required:
- Account and project created on the hosting platform
- Authentication token set as an environment variable
- Build output directory configured correctly
This works for production deployments — but it requires pre-configured projects and hosting accounts. It's also slower than a lightweight publish command when all you need is a review link.
Method 2: GitHub Pages or Static Hosting via git push
For Codex workflows that already use git:
# Push to a gh-pages branch
git checkout -b gh-pages
git add ./dist/*
git commit -m "deploy"
git push origin gh-pages
GitHub automatically publishes the branch at https://username.github.io/repo-name/. Clean for open-source projects; requires repo configuration upfront.
Method 3: One CLI for Instant Publish and Share
This is the approach where Codex publishes through the same CLI it uses for image generation, video generation, and file storage:
# Publish an HTML file to a live URL instantly
anycap page publish ./index.html --title "Product Landing Page"
# Publish a full directory
anycap page publish ./dist/ --title "Q2 Report"
# Returns a shareable URL immediately
# → https://page.anycap.ai/p/abc123
No account setup per project. No git repo required. Codex generates the page, publishes it, and returns a live URL — all in one command.
Install AnyCap for Codex:
npx -y skills add anycap-ai/anycap -a codex -y
anycap login && anycap status
Publish Patterns in Depth
Instant Page Publish
# Codex generates a landing page and publishes it for stakeholder review
anycap page publish ./landing.html --title "v2 Landing Page — Review"
# Returns: https://page.anycap.ai/p/xyz789
The URL is live immediately. No build step, no deployment pipeline, no hosting configuration.
Full Project Publish
# After Codex builds a React or Next.js project
npm run build
anycap page publish ./out/ --title "Feature Preview — Sprint 24"
Publish Generated Media with Context
# Publish a generated image with surrounding context page
anycap image generate \
--prompt "product hero shot, dark UI, neon blue accents" \
--model seedream-5 \
-o hero.jpg
anycap page publish hero.jpg \
--title "Hero Image Options — Please Review" \
--caption "Generated with Seedream 5. Dimensions: 1440×900."
A/B Variants for Review
# Two landing page variants, published to separate URLs
anycap page publish ./variant-a/ --title "Landing — Control Version"
anycap page publish ./variant-b/ --title "Landing — Experiment Version"
# Return both URLs for stakeholder comparison
Drive Upload + Page Publish: When to Use Each
| Use case | Best approach |
|---|---|
| Share a single file (image, video, PDF) | anycap drive upload — returns CDN URL |
| Host a webpage with navigation | anycap page publish — returns browseable URL |
| Embed an asset in a published page | Drive upload → get URL → embed in HTML → page publish |
| Long-term asset storage | Drive upload (durable storage) |
| Quick review link for stakeholders | Page publish (optimized for browser viewing) |
The Full Codex Build → Generate → Publish Pipeline
# Step 1: Codex builds the landing page
# ... Codex generates index.html, styles.css, assets/
# Step 2: Generate hero image
anycap image generate \
--prompt "developer tool landing hero, dark theme, code editor interface" \
--model seedream-5 \
-o assets/hero.jpg
# Step 3: Generate hero video
anycap video generate \
--prompt "interface comes to life, code highlights animate in" \
--model seedance-2 \
--mode image-to-video \
--param images=./assets/hero.jpg \
-o assets/hero-loop.mp4
# Step 4: Upload assets to get permanent CDN URLs
HERO_IMG=$(anycap drive upload assets/hero.jpg --format url)
HERO_VID=$(anycap drive upload assets/hero-loop.mp4 --format url)
# Step 5: Codex updates index.html with the live CDN URLs
# (Codex edits the HTML with the $HERO_IMG and $HERO_VID values)
# Step 6: Publish the complete page
anycap page publish ./ --title "Product Launch Preview"
Codex built the page, generated the assets, stored them at permanent URLs, and published a browseable preview — all in one session.
Cross-Agent: Same Commands, Different Agents
Publish commands work identically across agents. Only the skill installation changes:
| Agent | Install target | Unique publish advantage |
|---|---|---|
| Codex | ~/.codex/skills/ |
CLI-native — publish chains with && like any shell command |
| Claude Code | ~/.claude/skills/ |
Parallel publishing — Claude Code can publish multiple variants via subagents |
| Cursor | ~/.cursor/skills/ |
In-IDE — Cursor publishes and opens the review URL without leaving the editor |
FAQ
Does Codex have native publishing capability?
No. Codex can generate complete page code but doesn't have a built-in way to host or publish that code at a public URL. AnyCap's page publish command adds that capability through the same CLI Codex already uses for other tasks.
How long do published pages stay live?
Pages published through AnyCap remain accessible until you explicitly unpublish them or your account plan's storage duration is reached.
Can I update a published page after the first publish?
Yes. Run anycap page publish again with the same content. You can also publish to a named path to maintain a stable URL across updates.
Can I use a custom domain for published pages?
Custom domain support is available on higher-tier AnyCap plans. For review links and stakeholder previews, the default page.anycap.ai URL is sufficient.
Can Codex publish to production hosting (Vercel, Netlify) instead?
Yes — Method 1 above covers production deployment CLIs. Use anycap page publish for quick review links and stakeholder previews; use platform CLIs for final production deployments.
Can I use publish in automated Codex pipelines?
Yes. anycap page publish is headless. Set ANYCAP_API_KEY as an environment variable and call it from any Codex automation, CI job, or scheduled task.
→ Give Codex publish capability — one install, all capabilities
📖 What to Read Next
- How to Generate Images with Codex (2026) — Generate the assets you'll publish.
- How to Generate Video with Codex (2026) — Video generation companion guide.
- How to Give Codex Cloud Storage (2026) — Persistent file storage for Codex-generated assets.
- How to Give Codex Web Search (2026) — Research capability for the full Codex toolkit.
Related Articles
- What Is a Capability Runtime? — The infrastructure that bundles publish, image, video, search, and storage into one CLI.
- Terminal Agent Showdown: Claude Code vs Codex vs Windsurf — How Codex compares to other terminal agents on capability breadth.
- What Is an AI Agent? The Complete Developer Guide — Agent fundamentals: why publish capability is the last mile that matters.
Written by the AnyCap team. We build the capability runtime that gives Codex instant publish, cloud storage, image generation, video generation, and web search through one CLI — so your agent doesn't stop at the sandbox boundary.