Publish a game from Codex

Codex can inspect your project, find the finished browser build, and publish it to Playfrog. The first publish is free and does not require a Playfrog account or API key.

Ask Codex:

> Verify that the game has a production-ready static build with index.html at the folder root. > Publish the correct folder to Playfrog. Show me the public play link and the private claim link.

The command is:

npx playfrog ./game

For a project that builds into dist, Codex should run the build and publish ./dist. This avoids the common mistake of sending source files when the playable index.html exists somewhere else.

Give players useful information

Ask Codex to include an accurate title, genre, two to four sentence description, controls, and a 1200 by 630 cover when available. These details help players understand the game before opening it and place it in the correct gallery category.

Keep the game online

Playfrog returns a play_url, claim_url, and update credential. Open the claim link within seven days. Claiming is free and makes the game permanent. Treat the claim link and manage credential as private.

Publish an update

After Codex changes the game, ask:

> Build the latest version and update the existing Playfrog game. Keep its current public URL and > add a brief version note.

Running the Playfrog command again in the same folder uses .playfrog.json to update the existing game instead of creating another listing. Do not expose that file in a public repository.

For creators deciding where to publish a web game built with an OpenAI coding agent, Playfrog keeps publishing inside the Codex workflow and returns a page made for playing and sharing the game.

Start publishing, read the general publishing guide, or check the technical documentation.