Made level 2 or fixed a bug? Update your AI game at the same link

You sent the game to a group chat, and people played it. Now you have level 2, or someone found the bug that freezes the boss fight. You don't need a second link. The new file goes in as the next version of the same page, and everyone who has the link gets it the next time they open it.

This page covers what is different about a game. For the general steps, comparing versions, and rolling back, see how to update an AI-made page without changing its URL.

What stays when you publish the next version

• The link and the QR code. The page's Live URL doesn't change, so the link in the group chat opens the new version.
• Players' own saves. A best score or a "continue" save that the game keeps in the player's browser stays, as long as the address is the same and the new version reads the same names. The browser keeps saves per address, and Convika keeps each page's saves apart, not each version's.
• The shared scoreboard. Scores the game saves for everyone with Claude's window.storage and shared: true belong to the page. A new version reads the same board.
• Plays. Page views belong to the page, so you can compare plays before and after the update in the page's visitor stats.

Saves don't follow the game to a different address. If you move it to another subdomain or your own domain, players start from zero there. Shared scores do follow, because they belong to the page. MDN describes localStorage as storage "for the Document's origin", which is why the address decides.

Ask your AI for the whole new game, with the same save names

The one thing that loses saves in an update is the AI renaming them. If version 1 saved the best score as best and version 2 saves it as highScore, every player's best score looks gone. In the conversation that made the game, send:

Add level 2 after the current last level. Keep everything else as it is.
Keep every storage key and save format exactly the same as now, so players'
saved progress and the shared scoreboard still load.
Give me the complete updated game as one HTML file, from <!DOCTYPE html>
to </html>, with nothing shortened or left out.
After the code, list each change you made in one line.

If the save format has to change, ask the AI to read the old save and convert it the first time the new version loads.

If the conversation is gone, take the live version's HTML from the page's screen: in Version History, the row marked Live has Download HTML and Copy HTML. Paste it into a new chat with the prompt above.

Publish the new version in 4 steps

1. Open the game's page, not the main upload screen

Sign in at app.convika.com and open the game from your page list. Check that the Live URL is the link you shared.

2. Upload the new file as a new version

Under Update from an HTML file, click Upload a new version, choose Upload a file or Paste code, and click Upload as a new version. Uploading uses no AI credits.

3. Play the private preview

Preview v2 is ready appears with your version number. Open the preview and play through the changed part on your phone.

The preview keeps shared scores in that browser tab only, and they end with the tab. It never writes to the live scoreboard, so test scores don't reach your players.

4. Publish it at the same link

Click Publish v2 at the same link, then Publish in the dialog. Open the live link and reload: the new version is there, with the scoreboard as it was.

If the new version breaks something, find the old version in Version History, click Roll back to this version, then Restore. Free keeps the last 10 versions and Pro the last 50.

A second game is a different decision

Level 2 belongs in the same page. A different game, with its own link, is a new page.

A new workspace on Free has 1 live page at a time. Publishing a second game offers to Swap it in for the live page (free), and the swap takes the first game back to a draft: the link you shared stops opening. To keep both games live, the second one needs Pro. If you only want players to find the new game, add it to the first game as a new mode or level, and the link stays one.

Update it from Claude or ChatGPT over MCP

If your AI client is connected to Convika, ask it to update your game on Convika and keep the save names. It saves the new HTML as the next version of the same page and returns a preview link, which expires after 1 hour. It publishes only when you tell it to.

Frequently asked questions

Do I need to send a new link after updating my game?

No. Publish the new file as the next version of the same page, and the link you sent opens it. Players who have the game open in a tab see the new version after they reload.

Will players lose their saved progress when I update the game?

Not if the address and the save names stay the same. Saves in the player's browser are kept per address, and a shared scoreboard belongs to the page. Ask your AI to keep every storage key as it is.

Why does my game still show the old version?

Usually the new version was uploaded but not published: the page's screen shows "v2 is newer than the live page." with a Publish button. If you already published it, reload the game's tab.

Can I host two different games on the Free plan?

A new workspace on Free has 1 live page at a time. A second game can replace the first, which takes the first one's link offline, or both can stay live on Pro.

Sources

• Window: localStorage property (MDN Web Docs), read on October 27, 2026