OpenAI Codex release notes: Sites turns prompts into hosted web apps

OpenAI Codex release notes got a practical update on June 2: Sites is now in preview in the Codex app. That makes Codex more useful for small web apps, dashboards, and internal tools, as long as teams keep "save for review" separate from "publish live".

Source: Codex changelog, June 2, 2026

OpenAI Codex release notes: Sites is now in preview

The Codex app is OpenAI's desktop app for coding-agent work in local projects. A coding agent is an AI assistant that can read code, propose changes, and in some modes run commands in a project. Sites is a Codex plugin that can create, save, deploy, and inspect websites, web apps, and games hosted by OpenAI.

The interesting part is not another prototype. The useful part is that a prompt can now become something you save, review, and, once approved, publish without setting up a separate deployment chain.

Source: Sites - Codex | OpenAI Developers

What changes for small teams and internal tools

For Nordic businesses, schools, and organizations, Sites is most useful when an idea is too small for a full development project but too concrete to stay buried in a chat thread.

• A simple request view can become a saved version for the team to review.
• A dashboard can be tested with the right fields before anyone builds a permanent integration.
• An internal tool can use environment variables and secrets instead of pasted keys in a prompt.
• A published Sites URL is a production deployment. If you want review first, ask Codex to save a version without deploying it.

Source: Sites publishing workflow

Human step: check access first

This is not a CLI update, so do not start with terminal commands.

• ChatGPT Business has Sites enabled by default, according to OpenAI.
• ChatGPT Enterprise requires an admin to enable Sites through RBAC, or role-based access control.
• If Sites is not visible in the Codex app: open Plugins, find Sites, add it, and then start a new thread.
• Open Sites in the app sidebar to return to projects and manage hosted environment variables and secrets.

Source: Sites availability and setup

Short example: use the new Codex feature

After a human has checked that Sites is available in the Codex app and opened the right project, the agent prompt can be this short:

@Sites Review this project as a Sites candidate. Check whether the build can be saved as a version without being deployed. Propose the smallest required changes, list any environment variables or secrets needed, and stop before deployment.

Good output should:

• say whether the project looks compatible with Sites or needs changes first,
• separate a saved version from a published deployment,
• list environment variables, secrets, and access needs without asking for passwords in chat,
• end with a clear human decision: save, change, or deploy.

Where human control belongs

Sites makes quick prototypes easier, but the control point belongs at publication. Use scoped secrets, separate test data, approval before deployment, and a simple change log of what Codex saved or published. This is a good Tool Forge question: build a small, reviewable routine before connecting it to production systems.

What we are watching in the next Codex changelog

Sites is free during preview, according to OpenAI's pricing page, and more plans are expected later. For Hammer readers, the next question is not only the price. It is how well Sites fits existing environments, access rules, and internal support.

Source: Codex pricing - Sites