Clonez et lancez avec votre AI CLI

L'installation la plus native pour l'IA : ne tapez pas les commandes vous-même : remettez le dépôt à votre Agent de codage-CLI et laissez-le cloner, installer, lancer et renvoyer l'URL locale.

✅Open source (Apache-2.0). Le flux ci-dessous fonctionne avec n’importe quelle CLI de codage AI.

What the plugin adds to your client

Project awareness — Active game, project root, service state and next action are exposed through forgeax://status.
Engine knowledge — Version-matched Skills, declarations, templates and Engine source are installed into the project.
One-call preview — The agent builds or reuses the selected Runtime and receives the actual Play URL and logs.
Identity checks — Runtime and Engine SDK commits are reported together so the agent does not build against the wrong API.

1 · Connect your client once

Node.js 18 or newer is enough. Run the installer for the clients you use:

npx -y @forgeax/game install --ide codex

# Configure several clients in one pass
npx -y @forgeax/game install --ide codex,claude,cursor

Before it writes configuration, the installer launches the exact MCP command and completes a real initialize → tools/list → resources/list handshake. Existing config is merged; a changed file gets a .bak.latest backup.

Other supported client ids include zcode, opencode, windsurf, vscode, trae, codebuddy and workbuddy. Omitting --ide configures every supported client.

2 · Initialize a game project

Create or enter an empty directory, then ask the package to create a project and active game:

mkdir neon-runner && cd neon-runner
npx -y @forgeax/game init --game neon-runner

init creates the ForgeAX project, selects the game and materializes .forgeax/engine-sdk/ from the same Engine pin as the managed Runtime. Your game lives under .forgeax/games/neon-runner/.

3 · Open the folder in your AI client

Start a fresh session in the project directory and give the agent an outcome, not a list of Engine APIs:

FIRST PROMPT

Use ForgeAX Game to inspect this project, then build a small playable neon collectathon.
The player should move with WASD, collect 8 energy shards, show progress, and win.
Run the game in the verified ForgeAX Runtime, open the Play URL, test the controls,
and keep fixing it until the playable behavior is proven.

The installed Skill tells the agent to read project status, consult Engine Skills and declarations, edit only the active game, run the current game and verify the result in the browser.

What a healthy setup looks like

The client sees the ForgeAX MCP server and can read forgeax://status (or call forgeax_status_lite).
The project has an active game under .forgeax/games/<slug>/.
The Engine SDK and Runtime identities match; the launch result reports both.
The agent can call forgeax_run_current_game and receives a reachable Play URL plus log paths.

Useful maintenance commands

Command	Use it when
`forgeax-game doctor`	You want to check Node, client configuration, project binding and service tiers.
`npx -y @forgeax/game update`	An existing project should refresh the published command, client entries and project routing rules.
`forgeax-game use <slug>`	A project contains several games and you want to activate another one.
`forgeax-game devkit install`	Engine/game-development Skills are missing or need to be refreshed.

Pourquoi est-ce l’installation la plus fluide ? Parce que ForgeAX est conçu en premier lieu pour l'IA - même « s'auto-configurer » est quelque chose que nous sommes heureux de confier à un Agent.