AI Game Dev app and gamedev CLI

AI Game Dev is the AI game development app of AI Game Developer: an AI agent that understands your game project, edits its files and drives your engine editor through natural language. It comes in two forms that share one account, one background service and one chat history: the desktop app and the gamedev CLI for the terminal. This section of the wiki explains how to install them, sign in, open a project, pick models, extend the app with packages and fix common problems.

Desktop app or CLI#

Both frontends run the same agent, powered by the Claude Agent SDK, and both authenticate against your AI Game Developer account.

You can use both on the same computer. A chat started in one is kept in the shared history, and packages installed at the user level apply to both.

How it fits with the engine plugins and MCP#

The app does not replace the engine plugins; it uses them. Each engine has its own MCP plugin that exposes editor tools (create objects, edit scenes, run tests, take screenshots and much more):

• Unity MCP for Unity, managed by unity-mcp-cli.
• Unreal MCP for Unreal Engine, managed by unreal-mcp-cli.
• Godot MCP for Godot, managed by godot-cli.

When you open a Unity, Unreal or Godot project, the app detects the engine, offers to install or update the matching plugin, opens the editor when the agent needs it, and connects the editor's tools to your chat through ai-game.dev with your signed-in session. The installers ship inside the app, so you do not need Node.js or npm for the desktop app.

The plugins also work without the app: any MCP client (Claude Code, Cursor, VS Code, Codex and others) can connect to the MCP endpoint. The ecosystem overview shows how the app, the plugins and the MCP server fit together, and the tools catalog lists what the plugins give the agent.

What the app adds on top of the plugins#

• A chat agent that reads and edits your project files, runs commands and calls engine tools, with approvals you control.
• A choice of AI models from several providers, assigned by your plan and region. See Agents and models.
• A desktop workspace with one window per project, sessions in panes, file previews (textures, 3D models, audio, video) and Git. See Workspace.
• Packages that add whole capabilities: Blender, music with SuperCollider, a project Knowledge Base, Tripo 3D, local image and video generation on your GPU, and cloud video and audio models. See Packages.
• Session tools: each chat chooses which tools it carries, so the agent's context stays small.

Page map#

Start here if you are new:

1. Installation: install the desktop app on Windows, macOS or Linux, or the gamedev CLI, and keep them updated.
2. Sign-in and account: sign in, plans, usage shown as percentages, switching accounts.
3. Projects and engines: open or create a project and let the app set up the Unity, Unreal or Godot plugin.
4. Agents and models: pick a model, reasoning effort and agent, approvals, local models.

Then go deeper:

• Workspace: panes, previews, Explorer, Search and Source Control in the desktop app.
• Packages: what a package is, the Packages window, gamedev pkg, levels, updates.
• Packages catalog: every package available today and what it does.
• Creating packages: write, test and share your own package.
• CLI reference: every gamedev command and the slash commands in the terminal.
• Troubleshooting: sign-in, engine connection, packages and models.
• FAQ: short answers to common questions.

Quick start#

1. Download the app from the download page, or run npm install -g @baizor/gamedev.
2. Sign in with your AI Game Developer account.
3. Open your game project folder.
4. Describe what you want, for example "List everything in the active scene."

The four-step Quickstart walks through the same flow with screenshots, and the App guide gives a one-page overview. For prompting tips, read the best practices.