How to update a published web game

You can replace the files of a Playfrog game without creating a new listing or changing the link you already shared. The update can be handled by the same coding agent that published it.

Update from the original project folder

Make the changes, rebuild the game if needed, and run the same command:

npx playfrog ./game

The first publish creates .playfrog.json in the game folder. It contains the game ID and manage credential. On later runs, the CLI uses those values to update the existing game.

If the playable files are in dist, update with:

npx playfrog ./dist --notes "Added a new level and improved touch controls"

The game keeps the same playfrog.gg/g/... URL.

Update with your coding agent

Use a direct instruction:

> Build the latest version of this game and update its existing Playfrog listing. Keep the same > public URL. Add a short release note and show me the link when it is live.

Claude Code, Codex, Cursor, Windsurf, Copilot, and Gemini CLI can run the command. A connected chat assistant can use the Playfrog update_game MCP tool with the game ID and manage token.

Change the title, description, or cover

You can publish files and metadata together:

npx playfrog ./game --title "New title" --genre action \
  --desc "Updated description." --controls "WASD to move" \
  --cover ./cover.png --notes "Updated art and controls"

Creators who claimed their game can also use its manage page for supported edits and credential recovery.

Protect the update credential

Do not publish .playfrog.json or the manage token. Anyone with that credential can update the game. If a claimed game's token is lost, sign in as its owner and issue a new token from the manage page. An unclaimed game with a lost token must be published again.

Updates are free. Claim the original game within seven days so it remains available permanently.

Read the publishing guide, see agent-specific instructions, or open the complete documentation.