Troubleshooting
Fix common AI Game Dev app and gamedev CLI problems: sign-in, models, engine plugin and editor connection, packages, local and cloud generation.
This page collects the problems users of the AI Game Dev app and the gamedev CLI meet most often, with the likely cause and the fix. Find the symptom under its area: sign-in, models, engine connection, packages, local models, cloud generation or the CLI.
Sign-in
The sign-in browser window does not open.
No default browser is set, or a firewall blocked the sign-in. Set a default browser and choose Sign in again. Behind a corporate proxy, allow outbound HTTPS to ai-game.dev. In the CLI, /login shows a code and an address that you can open on any other device instead.
The app went back to the sign-in screen, or the CLI asks for /login.
Your session expired or was revoked, for example from the Connected devices page of your account. Sign in again; your chats and settings are kept.
A headless run exits with code 2.
The computer is not signed in, the prompt was empty, or the folder or a flag is not usable. Run gamedev interactively once and type /login. See the exit codes.
The wrong account is signed in.
The app, the CLI and gamedev acp share one sign-in per computer. Use /login --switch in the CLI, or sign out and in again in the desktop app.
More about the flows: Authentication guide.
Models
The model list says it is loading or unreachable. The list comes from ai-game.dev. With no connection and no saved copy of the last list, there is nothing to show. Check your connection and reopen the picker.
A model is greyed out. The reason is shown under its name: it may need a higher plan (see the pricing page), it may not be offered in the country of your billing address (see model availability), or it may require age confirmation in your account. The bottom of the model list shows the region your availability is based on.
--model is refused in the CLI.
The model is not available to your account. Pick one with /model or pass another id.
Usage runs out quickly. Usage is shown as a percentage of your monthly allowance. Larger models use more of it for the same work; use a faster model for routine edits, and keep only the tools a session needs switched on.
Engine plugin and editor connection
The CLI says there is no Unity, Godot or Unreal project in the folder.
Open the project's root folder: for Unity the folder with ProjectSettings/, for Godot the folder with project.godot, for Unreal the folder with the .uproject file.
The plugin did not install.
The engine or the project could not be found. Make sure the engine is installed (Unity Hub, Unreal Engine or Godot) and that you opened a real project folder, then click Install Package in the sidebar or run /install-plugin. To install by hand, follow the guide for Unity, Unreal or Godot.
The sidebar offers Update Package. A newer plugin version is available. Click it to update the plugin in the project.
The editor shows "Disconnected". The editor has not finished authorizing, or lost its Cloud connection. Open the AI Game Developer window in the editor, choose Cloud, click Authorize and wait for Ready.
The agent waits a long time for the editor. Large projects take a while to open. The app waits up to 15 minutes for the editor to start and up to 2 more minutes for its tools. Press Stop to cancel the wait; an editor that already started stays open. Opening the editor yourself before a long session avoids the wait.
Creating a project says the engine editor is not installed. Install the engine first, or choose an installed editor by hand in the create dialog.
Packages
"requires AI Game Dev >=X, you have Y". The package needs a newer app. Update the app (see Installation).
A package shows a warning count.
Open the Packages window, select the package and read its Errors tab. The app log has the details under pkg:<id>.
Packages stopped working in a project.
If the package host crashes three times within five minutes, it is not restarted automatically. Click Reload in the Packages window, or run /packages reload in the CLI.
A package does not update.
Automatic updates are per package and per computer: check its Auto-update switch. Packages from a local folder and GitHub sources pinned to a tag never update automatically. Use Check for updates or gamedev pkg update <id>.
A version is marked "not in registry anymore". That version was withdrawn. It keeps working and is never offered as an update target.
A package is blocked because a dependency is excluded.
The dependency is turned off at some level of this project. Choose Include it again in the Packages window, or gamedev pkg include <id>.
"Tools of package X are unavailable in this session". An MCP server with the same name is already configured for the session (by you, the project or an engine). Rename or remove the other server in Settings, MCP servers.
A linked package folder does nothing.
id-mismatch means the folder's manifest names another package; not-found means the folder moved. Run gamedev pkg unlink <id> to go back to the published version.
A tool is missing from the chat.
Installed packages do not add tools to every chat. Switch the tool on in the session's Tools row (CLI: /config, Tools). The change applies from the next message.
Local image and video models
A model is not offered for my computer.
Each model lists the hardware it fits; the app offers only what your GPU, video memory and driver can run. If you changed hardware or drivers, run /images redetect. See the hardware table.
Generation fails with "out of memory" or is very slow.
A run that runs out of video memory is retried once with a smaller memory budget. A silent fallback to the CPU is reported as a failure rather than hidden. Try a lighter model (for example a Lightning variant or Z-Image Turbo), or close other GPU-heavy programs. /images stop cancels queued images and frees the GPU.
The disk is full.
Move the model storage to a larger drive in Settings, Model storage, or with /images storage <new folder>; /images free-space deletes files no model uses.
The image runtime was blocked or is broken.
Run /images reinstall to set it up again.
Cloud generation
The agent says Cloud generation is not turned on.
Switch on Cloud generation in the session's Tools row, or use /cloud ask in the CLI.
A cloud model cannot be used. Cloud generation is for paid plans, some models need Studio or higher, and some are not offered in every region. The Models tab marks the reason. A failed job does not use your allowance.
SuperCollider and Blender
Music does not start on Linux. The SuperCollider runtime is available on Windows and macOS today.
Blender is not found.
Run /blender list to see every Blender the app finds, /blender setup to set it up again (optionally with the path to your Blender), or let /blender download a portable Blender. Blender 4.2 or newer is required.
CLI and background service
The CLI is out of date.
Run gamedev update.
"The running host does not offer … yet. Quit every AI Game Dev window and CLI, then start again".
The background service is older than the CLI or app you started. Close every AI Game Dev window and CLI and start again, or use /update now in the CLI.
I need logs for a bug report.
gamedev daemon status shows the state of the background service and gamedev daemon logs --lines 200 prints its recent logs. Share the relevant part, never your credentials, on Discord or GitHub.
Still stuck
Check the FAQ, the site FAQ and the release notes for recent fixes.