Join the waitlist

Getting started

Make a small game, play it against the real Engine, then bring your own.

Set up Gamestage first: it adds Gamestage to Claude, Claude Code, Codex, Cursor or a terminal. This chapter then makes a small game, plays it against the real Engine, and brings your own.

Starting a new game? Use create (step 2). Already have a browser game? Use inspect (step 3).

Seeing the formats, scaffolding a game, inspecting a prototype and validating a manifest need no account. Playing against the real Engine with dev and verify needs you signed in: gamestage login creates the account the first time, and you can play straight away, before anybody has approved it. Deploying needs the account approved by someone at Monterosa. Your account says more.

Every example says gamestage <command>. Run it as npx gamestage <command>.

1. Read what your agent reads

The agent does the migration. The CLI inspects, serves and proves it worked. Set up gave your agent its instructions. To wire an agent by hand, the text is at /agent.md, with the fuller entry point at /start.md. Both are plain Markdown, written to be read once.

Every chapter of this documentation is also served as raw Markdown and JSON: add .md or .json to any docs URL.

2. Make something small first

gamestage formats
gamestage create --name "My Game" --format hunt
cd my-game          # only if create says it made a folder
gamestage login
gamestage dev --serve

formats says what each format is, with a game of that kind to play, so you choose knowing what you get. create writes gamestage.yaml, an index.html, the two generated browser clients and a favicon. Run by hand with no flags, it asks for the name and the format instead. In a folder that already holds other things, it makes a folder named after the game. login creates the account dev and verify need, or signs you back into one you already have; they run once Monterosa has approved it. dev --serve serves the game's page on your machine and plays a sample round on the deployed Engine, as test plays that reach no leaderboard, and prints the address to open. It needs a network connection.

Play the game and get one wrong. The attempts count down because the Engine said so, and the page draws what it was told.

create scaffolds a playable page for hunt, push, group, predict, bingo and shoot. Read Game formats for the detail. For a format we do not have yet, run gamestage suggest "what you want to build".

Then prove it:

gamestage verify

verify exits 0 only when every check passes. Any other number means something is open or unproved, and the output says which.

3. Bring your own game

If you already have a prototype, let the CLI read it:

gamestage inspect . --write

Source inspection is read-only. --write adds gamestage.yaml and refuses to replace an existing one unless --force is present. The report separates what stays in the interface, what has to move behind the Engine, what platform support is missing, and what needs a person to decide.

From there, follow Build and deploy, which is the same route in detail.

If a command differs from this guide

npx caches, so npx gamestage can keep running a version you downloaded weeks ago. npx gamestage@latest <command> always fetches the current one. gamestage start prints the version it is, so compare that against the current one before assuming a page here is wrong. Nothing checks for you: the CLI never calls home.