Before you start
You need a game you have already made, a coding agent such as Claude Code or Codex, a terminal open in the game's repo, and Node 22.13 or later.
When you finish, your game runs with its answers on a server instead of in the page. A content producer can then edit the setup of the game and create the content.
Some key terms:
| Word | What it means |
|---|---|
| Round | One go at your game. A quiz calls it a round, a vote calls it a voting window, a bracket calls it a tournament, and your game picks the word. |
| Play | One person's attempt at a round. |
| Engine | The server that holds the answer, counts attempts and decides the result. |
| Producer | Whoever writes the content once the game is live. Often not you, and often not technical. |
| Format | Which set of rules the Engine runs for your game. Game formats covers the ones that run today. |
The account decides how far you get before you have to stop:
- Onboarding, orienting, inspecting, writing the manifest and rewriting the page need no account at all. They happen on your own machine.
gamestage devandgamestage verifyneed you signed in, not approved. Each plays your round on the real Engine, under a practice name no fan sees, so you can play your game the day you sign up. Before approval an account can register three games.gamestage deployandgamestage promoteneed an account approved by Monterosa. The deploy is where the game reaches a fan. Until then, these say the account is waiting. Before you can deploy you accept the Terms of Service yourself, on the approval screen: your agent hands you the address and waits. If your organisation has a signed agreement with Monterosa that covers Gamestage, that agreement stands in for the Terms and you are not asked. Personal email addresses such as Gmail can practise but cannot apply.
Your agent does most of the work. You sign in, review the manifest, decide what moves, check what a deploy will publish, and run the command that moves a game to prod.
Set up Gamestage
Add Gamestage to your coding agent as Set up describes. For Codex, Cursor and most other agents that is one command:
npx skills add https://gamestage.ai/skillNothing is installed globally. The skill is a set of instructions plus the address of the tool, and the tool runs from npm each time you call it. You do not need an account, and nothing leaves your machine.
Check your project
npx gamestage startThis reads the current directory and tells you the next thing to do. Run it whenever you are unsure. Your agent runs it first in every session, because it has no memory of the last one.
Inspect the game
npx gamestage inspectThis reads your game and writes a report: what it is, what it holds, and which parts a player can currently read that they should not be able to. Your agent works from the report, because a prototype is often one big HTML file with all the data inside it.
Decide what has to move
No command here. You decide.
Ask which facts decide the outcome. Anything a player could read off the page and use to win has to move to the Engine. Everything else can stay where it is.
Your agent matches the report against the six game formats and proposes one.
If your game is a quiz or a straight prediction, the answer can stay on the round in Studio, where a producer sets it, and the Engine marks each play against it. Game formats says which format that is.
Create the manifest
npx gamestage create --name "My game" --format pushThis writes the App Manifest, a file called gamestage.yaml that says what your game is, which rules it runs and who owns which fact. --format is where the format goes, and push is one of the six.
The name is what a fan reads. Every later command takes the game's id instead, which create mints as your name plus four random characters and writes to app.id in gamestage.yaml. "My game" becomes something like my-game-a3c9, and yours will end differently. Read the id out of the manifest before you deploy, because the deploy does not accept the title in its place.
Your agent fills the manifest from the report. Review it before you go on. The tool refuses a manifest that contradicts itself, so a bad one cannot reach a deploy.
Rewrite the page
npx gamestage client --out .This writes two files into your game's folder: gamestage.js, the Gamestage library, and gamestage-player.js, the player client it uses to talk to the Engine. Your page then asks the Engine for the round and sends each play to it, and works nothing out itself. The player API is the contract between them.
This is the largest edit in the process. Your agent makes it, bounded by that contract.
Sign in
npx gamestage loginThis signs you in, and creates an account if you do not have one. There is no website step first.
Everything above this step works without an account. This is the first step that needs one, because the next two run your game through a real Engine rather than reading your files.
Run the game locally
npx gamestage devThis serves your game against an Engine on your own machine. Nothing about the game goes anywhere else: the round comes from your manifest and the marking is real.
Your agent runs it and plays the game in a browser. A page can return a healthy response and still be blank, because the code that breaks it runs in the browser, so playing it is the only proof.
Check the game
npx gamestage verifyThis runs a series of checks:
- the round played here is this game's own, with a real limit on attempts
- the answers are gone from what a deploy would publish
- the page reads every setting a producer can change
- the client is present and is the only way in
- a real browser gets its deadline from the server, plays a round through to a result, and notices the connection dropping and returning
verify needs you signed in, for the same reason dev does.
Fix a failed check
No command. Return to the step that broke. Your agent reads each failing check, which is written in the words of the fix, edits, runs verify again and reports what happened.
Deploy the game
npx gamestage deploy <game-id> --dir .This uploads the game, sets it up on Monterosa and gives you back a URL. The argument is the app.id from your manifest, not the game's name.
A deploy publishes a whole folder, so look at what is in yours first. Anything sitting beside your game goes up with it, including files that hold the answers. Your agent runs the deploy and reads back everything the service says, including anything it refused.
Move the game to prod
npx gamestage promote <game-id>You run this command yourself. It changes which audience a game is entitled to reach, so an agent hands you the command and its consequence rather than running it.
The command approves your own game to move from dev to prod. Approving your own game is not a purchase, so this works for any game that exists, is not archived and is not already approved, and there is no queue behind it. Run it again on a game that is already approved and it reports there is nothing to do, rather than approving it a second time.
It does not move the game on its own. Prod also needs your workspace on a paid plan, and only Monterosa can move it onto one: no command captures payment and none grants a paid plan on your word. Talk to us, and Plans and limits covers what Publisher and Enterprise are.
The command says which of the two states you are in when it finishes. Either your workspace already carries prod, or the game is approved and still counts as dev until we move the workspace, which then takes effect with nothing further for you to run. Your approval is recorded once, so a workspace that moves onto a paid plan later carries its approved games across without being asked again.
Serving does not read the approval. A deployed game is reached the same way and plays the same way whichever of the two states it is in, so promoting a game today records the decision and changes nothing a fan meets.
Promotion changes no files and mints no version. The game keeps its id, its scores and its leaderboard.
Free a slot
npx gamestage suspend <game-id>Starter runs one live game at a time. Suspending an old one makes room. Plans and limits has the detail.
Let players in
Send them the URL from the deploy. They install nothing and need no account, and the round comes from the Engine.
Hand the game to a producer
Your deploy prints a link to Monterosa Studio, the tool a producer uses. Studio is Monterosa's product and keeps its own name.
In Studio the producer sets the game's name, its description, the how-to-play text, the wording on the main button and the colour. Those reach a player on their next visit, and anyone already playing sees them change without reloading.
Write the next round
The producer writes the next round in Studio and it goes live. Nothing is rebuilt and nobody deploys.
If none of this fits
Use this when the process does not work for the game you have.
npx gamestage suggest "what you were trying to build" --closest groupThis tells us about a format or a feature that does not exist. It needs no account. It prints exactly what it would send and sends nothing until you add --send. It sends four short pieces of text and never your game, your manifest or an answer.