CLI reference.

Needs

Node.js 20 or later. The CLI has no dependencies of its own: only Node and its built-ins. Signing in needs a phaser.io account.

Without installing

$ npx -y @phaser-ae/cli <command>Copynpx fetches the latest version from npm

Installed

$ npm install -g @phaser-ae/cliCopythen: phaser-ae <command>

In a game's folder

The folder keeps its own copy of the CLI, in phaser/cli, and its commands are npm scripts: npm run -s build, npm run -s publish -- "…" and the rest, below. phaser-ae update brings that copy and the engine up to date.

License

MIT, for the CLI. It doesn't cover the Phaser AE engine or the expansion packs the CLI downloads.

When

Any command that needs phaser.io signs in first if it has to; one whose token is refused signs in again, once. login does it on purpose.

How

Your browser opens at phaser.io/account/agent/connect: sign in (or make an account) and approve Phaser AE. The page hands the token back to a one-off server the CLI runs on 127.0.0.1, which waits up to ten minutes.

While it waits

A command waits 100 seconds in an agent's shell, or five minutes at a terminal, then stops and says to approve and run it again. A command run meanwhile joins the same sign-in.

Where it's kept

~/.config/phaser-ae/config.json, readable only by you (PHASER_AE_HOME moves the folder). For the engine and the packs, the CLI trades it for a token that lasts six hours.

Signing out

phaser-ae logout, or revoke its token in your account on phaser.io.

The file

phaser-ae/SKILL.md, in the folder each coding agent reads its skills from: ~/.claude/skills for Claude Code, ~/.cursor/skills for Cursor, and so on for all 76. Codex's copy has agents/openai.yaml beside it, for how the ChatGPT app shows it.

What it does

Tells the agent what Phaser AE is, how to get Node.js, how to start a game in a folder of its own, and to follow that folder's brief from there. It's for Phaser AE alone: a request for the open-source Phaser library is left to the agent as before.

Which agents

Every one it finds on the computer, by its app, its command or its settings folder. Agents that read the same folder share one copy.

Kept up to date

build, blank and login write it too, for an agent whose copy is missing or from an older CLI. A SKILL.md the CLI didn't write is left alone.

Taking it out

$ npx -y @phaser-ae/cli setup --removeCopyremoves only the copies the CLI wrote

my-game/
  CLAUDE.md, AGENTS.md   the brief: Claude Code reads CLAUDE.md, every other agent AGENTS.md
  package.json           the folder's commands, as npm scripts
  .phaser/build.json     the game's build on phaser.io: its design, its id, the site
  .claude/               the folder's commands allowed in Claude Code, and the game in the Claude app's browser pane
  design/                the game design document, its pictures and sounds, your playtest notes
  game/                  the game's code, yours to read and change; its packs in game/node_modules/@phaser-ae
  phaser/                Phaser AE: the engine, its tools, and the folder's own copy of the CLI

The brief comes from phaser.io, so it keeps up with the engine. The folder can be moved or renamed: .phaser/build.json keeps it tied to the game.

Your agent runs these: you only need setup. Outside a game's folder they're phaser-ae <command> (or npx -y @phaser-ae/cli <command>). Inside one, most are npm scripts, written here as the script with its arguments after --.

--site <url>

Talks to another phaser.io, such as a development server.

--help

Every command, with what it does.

Check the computer

$ phaser-ae doctorCopy--fix gets the browser games are played in

Waiting for approval

A command that says it's waiting for you to approve Phaser AE: approve it in the browser tab it opened, then run the command again.

Codex

Codex needs to reach the network and write outside its folder, for the CLI's downloads and your sign-in: allow it when it asks, or give it full access.

Windows

If you installed Node.js while Claude Desktop was open, restart the app so it can find it.