Can Codex deploy my game for me?

Codex edits the code. Where the game runs depends on your setup: connect the repository to a host that builds from it, and merged changes go live. Check Codex's current docs for what it can run for you.

What should the repo contain so a host can build it?

A package.json with a build script and a note of the output folder, or a plain index.html. Give the host the build command and the folder.

How do I stop an agent from changing how the game feels?

Ask for small tasks and write the values you want kept, such as speed and jump height, in the README. Play the preview before you merge.

Which link should I give Foundplay?

The production address. Preview links can expire or ask for a login, and Foundplay checks that a listed link loads.

I built a game with Codex. Where do I share it and get players?

Codex works inside a code repository and hands changes back for you to review, so a Codex game is a repo, not a live site. Connect the repo to a host that builds on every push, check each change on a preview link, then list the main link on Foundplay. Keep the link you share pointed at a version you have tested.

Updated October 10, 2026. Written by Foundplay, a game discovery platform for free browser games. Foundplay also sells Boost, a paid promotion for games, and this guide says where it fits. The advice before that part works without it. All guides

The repo is the product

Put the project on GitHub and connect it to a host that deploys from a repository. GitHub Pages, Netlify, Vercel and Cloudflare Pages all do. The main branch is your live game: whatever is merged there is what players see. Decide that rule first, since an agent that opens many changes makes it easy to merge something you haven't played.

Use preview links for each change

Netlify, Vercel and Cloudflare Pages can build a preview of a branch or pull request at its own address. Play each preview on a phone before you merge. Some hosts put previews behind a login. Those links are for you, so don't share them, and don't give them to Foundplay.

Review what the agent changed

Read the diff for deleted files, new packages and new network calls.
Check the size of the build folder before and after. A change that triples it will slow the first load.
Ask what it tested and how, then play the same path yourself.
Compare the numbers you care about, such as jump height and enemy speed, since an agent can retune a game while fixing a bug.

Write tasks as game tasks

Small, specific tasks come back better. 'After losing, the score doesn't reset. Reproduce it, fix it and add a check' works. 'Make the game better' doesn't. Good first tasks for a web game:

Touch controls: left half of the screen moves, right half jumps.
A loading bar for the images and sounds.
Open Graph tags and a share image.
A pause when the tab is hidden.

A release routine

Before every merge: play the preview start to finish, check it on a phone, read the browser console and write one line about what changed. Tag the version in Git. If a bad change reaches the main branch, revert the merge instead of patching live, so the game is back to a known state in minutes while you work out what went wrong.

After it is live

Collect reports from players, turn each one into a task, and ship the fixes as updates. Each update is a reason to post again, with a one-line changelog.

How Foundplay can help

Foundplay is a game discovery platform for free browser games. It doesn't host games: every listing sends players to the creator's own site.

The free listing

Listing a game is free. Paste the link where people play it at /submit, check the details and publish. The game goes live right away, and Play sends players to your own site.

Paste the main address, not a preview. The source link field can hold the repository. Foundplay checks listed links every few hours and hides a game whose link fails twice in a row, so an expired preview link would take it down.

Boost, the paid option

Foundplay sells Boost, so it has a reason to want you to buy it. The free listing works without it.

A boost sends plays to your link for several days, so merge only tested changes while it runs. The plan called Boost fits a release you have just finished.

The Boost plan costs $10 for 120 plays in 5 days, which works out to 8.3¢ a play. Where it shows: its genre pages and search results.

A play is a counted click on Play from a sponsored spot, the same way public play counts work: once per game per network a day. Every sponsored spot is labelled Sponsored, and the share of plays not delivered by the end of the plan's days is refunded automatically. Foundplay can't see what players do after the click. Fan games and copies of commercial games can't be boosted. A game has to be listed before it can be boosted. List it first, or start a Boost and add your play link there, and Foundplay lists the game for free as part of the same flow.

For scale, Foundplay's own visit counter shows an average of 4,500+ visitors a day over the last three full days, and 600+ games are listed. It updates every few minutes.

List your game for free Boost with Boost See all Boost plans

More free ways to find players are in the full guide.

Questions

Can Codex deploy my game for me?: Codex edits the code. Where the game runs depends on your setup: connect the repository to a host that builds from it, and merged changes go live. Check Codex's current docs for what it can run for you.
What should the repo contain so a host can build it?: A package.json with a build script and a note of the output folder, or a plain index.html. Give the host the build command and the folder.
How do I stop an agent from changing how the game feels?: Ask for small tasks and write the values you want kept, such as speed and jump height, in the README. Play the preview before you merge.
Which link should I give Foundplay?: The production address. Preview links can expire or ask for a login, and Foundplay checks that a listed link loads.