Can you make a Codex Site public? Not under the documented model.

The short answer

As of June 6, 2026, there is no documented way to make a Codex Site public. OpenAI's docs describe exactly three access modes, and every one of them requires the viewer to be an active member of your OpenAI workspace. There is no public mode, no link-only mode, and no anonymous or external-viewer option, and there is no toggle to "make a site public."

On availability, Sites in Codex is in preview for ChatGPT Business and Enterprise workspaces only, with OpenAI describing more plans as rolling out later. Enterprise enables it through RBAC. So the two questions in the title have the same shape of answer right now: the capability people are looking for is not documented yet. OpenAI has signaled that the plan side will widen, but the docs name no specific plans and no public-viewer mode.

The rest of this post is the detail behind that, kept current. We mark roadmap talk clearly so you can tell what is documented from what is a statement of intent.

The three access modes, and why there is no public toggle

Codex Sites controls who can view a deployment at the workspace level. OpenAI documents three modes:

• admins_only, visible to the site owner and workspace administrators.
• workspace_all, visible to all active users in the workspace.
• custom, visible to specific active users or workspace groups you choose.

The common boundary is the important part. Every documented mode requires the viewer to be an active member of your OpenAI workspace. The custom mode looks like it might be the escape hatch, but it is not: the specific people you name still have to be active users or groups inside your workspace. So there is no documented setting that turns a Site into something an anonymous visitor, a client, or anyone without a workspace seat can open. That is why the answer to "make it public" is "no documented public option" rather than "use this option."

This is a coherent design for what Sites is built for. The feature is positioned around internal team tools, and for an internal tool "only people in our workspace can see this" is the right default. The friction shows up only when the thing you built needs to reach someone outside the company, which is a different job.

Which plans have Codex Sites today

Sites in Codex is in preview, available to ChatGPT Business and Enterprise workspaces only, with OpenAI describing more plans as rolling out later. The docs name only those two plans and list no specific plans for the rollout. Here is the documented state as of June 6, 2026.

To be precise about the "not documented" row: OpenAI has not named any other plan as supported, and it has said more plans are rolling out later without saying which. That is a statement of direction, not a release for any specific plan. If you are not on Business or Enterprise today, you should plan around not having Sites yet.

What "non-team plans ASAP" means, and does not

OpenAI has signaled wider availability, but only in roadmap terms, and not in the documentation. The launch landed on June 2, 2026; the roadmap post followed on June 4. On that date, Rohan Varma of OpenAI's Codex team posted on X that Sites is "live in Codex for teams," that improvements will ship constantly over the coming weeks, and that the team is "working hard to launch it to non-team plans ASAP."

Two things matter about how to read that. First, it comes from an X post, not the docs, so it is intent rather than a committed feature. We attribute it to the post for exactly that reason. Second, "ASAP" is not a date. It tells you non-team plans are on the roadmap; it does not tell you when, and it does not tell you that a public-viewer mode is part of the plan at all. The plan-availability question and the public-link question are separate, and the X statement speaks to the first, not the second.

The demand for the second is on record too. In the June 4 announcement thread, one user replied that they would love public links without authentication and said they could not find a way to make a site public yet. We note that as one user in the announcement thread, not as a commitment from OpenAI. It is useful signal that the public-link gap is felt, nothing more.

How to get a public link for agent output today

Full disclosure: this section describes Stacktree, which is our product, so read it as us explaining where we fit rather than as neutral advice. If what you actually need is a public URL for something an agent produced (a page anyone can open, with no login and no workspace seat), the practical pattern today is different from Sites in Codex, and it is worth being honest about both what it does and what it gives up.

The pattern is not to extract or export a Codex Site. There is no documented way to do that, and Stacktree does not do it. Instead, you have the agent render a static HTML view of what you want to show, then publish that HTML to an open host. Codex can do this directly: it can generate the HTML and call a publish tool over MCP, without leaving the session.

Stacktree is the open host in that pattern. It is an MCP-native publish primitive, so it works from Claude Code, Cursor, Codex, and Claude.ai rather than inside one agent. Its sharing model is the inverse of workspace-scoping: a site is private by default, and the unguessable URL is the credential, so the viewer needs no account and no workspace seat to open it. You can add a shared password, an email-domain gate verified by magic link, or end-to-end encryption if you want more than the URL. Custom domains are available on the Pro plan via Cloudflare for SaaS, update_site replaces the content in place at one stable URL, and it is source-available and self-hostable on your own Cloudflare account (Workers, R2, and D1). Pricing is a flat $0, $8, or $19 per month, never per seat, and the free tier plus an anonymous 24-hour first publish lets you try it with no account.

The trade is real and you should weigh it. Stacktree hosts static HTML only. There is no server logic, no application database, and no in-browser editor. So if what you need is a full internal app with persistence, the kind Codex Sites is built to deploy with D1 and R2 behind it, Stacktree is not that, and Sites in Codex is the right tool. Stacktree fits the narrower case: a page anyone can open by link, with no login, on your own domain if you want, that you can take with you. The two are not substitutes; they answer different questions.

What would change this answer

This is a living status post, refreshed whenever OpenAI ships a change. As of June 6, 2026 the answer is no documented public mode and Business and Enterprise only. Here is the watch-list that would move it:

1. A public or link-only viewing mode. If OpenAI documents a way to expose a Site to viewers outside the workspace, the headline answer flips. This is the single most-asked change.
2. An anonymous or password-only share option. Short of full public, a way to share without a workspace seat would partly answer the demand seen in the announcement thread.
3. Availability on more plans. OpenAI says more plans are coming without naming any. When a specific plan beyond Business and Enterprise is documented, the plan table above changes.
4. Custom domain support. Not documented today. If it lands, the OpenAI-hosted URL stops being the only option.
5. Export or self-hosting. Not documented today. A documented path to download the code or move a deployment would change the portability picture.

If any of these is documented, we will update this post and note the date. Until then, the answers above reflect the documented state of Codex Sites and are dated accordingly.