Does this replace a CI preview?

No, and it isn't trying to. It's for the times when setting one up costs more than the question is worth.

Can I host a backend change?

No. This serves static files, so it suits front-end work.

Will secrets in the build be exposed?

Yes — anything in a static file is public. Never publish a build containing real credentials.

Delete the address and it stops working immediately, along with every version of it.

Is there a limit on how many I can have?

Publish as many as you need; each gets its own address.

Host what Codex built, without touching your deploy setup

Codex opens the pull request and leaves you a working branch. Publish the build to show it to someone before it merges.

You can host:

Drop your Codex build folder here

Any other file works too — up to 25.0 MB, or 100.0 MB for a whole site

Free to use, live at your-name.99helpers.site in about ten seconds.

Why the last step is the slow one

Codex works through a task and hands back a branch, which is the right output for real software and a slightly heavy one for a quick look. Getting a preview in front of a designer or a stakeholder normally means a preview environment, and preview environments are exactly the sort of infrastructure nobody wants to set up for a one-off question.

What Codex gives you

A working branch or pull request against your repository
Static builds you can produce from that branch
Standalone scripts and pages written on request

A diff isn't a demo

Asking a non-developer to read a pull request to see a design change is asking the wrong person to do the wrong job.

Preview environments are heavy

Configuring per-branch deployments is worth it for a team and disproportionate for a single question.

Local only means local

Checked out and running on your machine, the change is visible to precisely one person.

Putting Codex output online

1
Check out and build
Pull the branch and run the project's build to produce a dist or build folder.
2
Drop the folder in
Drag it into the box above. Nothing to configure and no repository to connect.
3
Send the link
Give the address to whoever needs to look, and delete it after the decision is made.

Worth knowing

Name the address after the branch or the ticket — feature-new-checkout — so several previews stay distinguishable.
Publish build output only; source folders are large and unnecessary.
Deleting an address takes one click, which keeps throwaway previews from accumulating.
Password-protect a preview of unreleased work.
Publish successive builds to the same address so reviewers keep using one link.

Questions

Does this replace a CI preview?: No, and it isn't trying to. It's for the times when setting one up costs more than the question is worth.
Can I host a backend change?: No. This serves static files, so it suits front-end work.
Will secrets in the build be exposed?: Yes — anything in a static file is public. Never publish a build containing real credentials.
How do I clean up?: Delete the address and it stops working immediately, along with every version of it.
Is there a limit on how many I can have?: Publish as many as you need; each gets its own address.

Try it with what Codex just made you

Drop it in at the top of this page and see the link for yourself. You only make an account once it's ready to go live.

Back to the top Every AI tool we cover

Hosting artifacts from other tools

Hosting guides by file type

Everything gets its own address on 99helpers.site — see AI artifact hosting for every tool or free file hosting for any file type.