# Sign-in and account Sign in to the AI Game Dev app and gamedev CLI, switch accounts, understand plans and usage percentages, and manage your other devices. _Last updated: 2026-11-04_ The AI Game Dev app needs an AI Game Developer account. Signing in connects the app to your plan, your model list and the engine connection through ai-game.dev. This page explains how sign-in works in the desktop app and in the `gamedev` CLI, how plans and usage are shown, and how to use the app from your other devices. ## Sign in to the desktop app 1. Start the app. If you are not signed in, it shows the sign-in screen. 2. Choose **Sign in**. Your default browser opens the ai-game.dev sign-in page. 3. Sign in (or create an account) and approve the request. 4. Return to the app. It confirms your account and loads your models. There is nothing to copy or paste: no API key and no token. If the browser window does not open, set a default browser and try again; behind a corporate proxy, outbound HTTPS to ai-game.dev must be allowed. ## Sign in to the gamedev CLI Run `gamedev` and, if the computer is not signed in yet, type: ```text /login ``` The CLI shows a code and an address. Open the address on any device, check that the code matches and approve. This is the standard device-authorization flow, so it also works over SSH or on a machine without a browser. To sign out: ```text /logout ``` ## One sign-in per computer The desktop app, the CLI and the `gamedev acp` agent for ACP clients share one sign-in on a computer. Sign in once in any of them and the others use the same account. A sign-in started from an ACP client such as T3 Code never switches the account of a computer that is already signed in. To change the account of this computer from the CLI, use: ```text /login --switch ``` Your refresh token is kept in the operating system's credential store (Keychain on macOS, Credential Manager on Windows, the Secret Service on Linux), not in a project file. **Note** If a session expires or is revoked, the desktop app returns to the sign-in screen with the reason, and the CLI asks you to run `/login` again. Your chats and settings are kept. The details of the OAuth flows, Personal Access Tokens for CI and connecting your own MCP client are in the [Authentication guide](https://ai-game.dev/docs/auth). ## Plans Your plan decides which models and paid tools the agent can use. The current plans are **Free**, **Indie**, **Studio** and **Studio Max**, and there is a free trial. Compare them on [the pricing page](https://ai-game.dev/pricing). In short: - Some features work on every plan, such as the engine plugins with your own MCP client, Blender, music with SuperCollider and local image generation on your own GPU. - Hosted chat models, cloud image, 3D, video and audio generation depend on the plan. Some models and tools need Studio or higher. - A model or tool your plan cannot use is still listed, with the reason under its name (for example an upgrade hint), so you can see what is available. ## Usage The app shows your usage as a **percentage of your monthly allowance**: 100% is the full allowance of your plan. Each chat turn, and each paid operation such as a Tripo 3D model or a cloud video, uses part of it. Faster, smaller models use a smaller percentage for the same work than the largest models. When the allowance runs out, usage can continue from your extra balance only if you turned on Extended usage on your account page; it is off until you turn it on. Paid operations always ask first: a job card shows what the operation uses, and you approve it once, for the whole session, or up to a budget you set as a percentage of your allowance. Local models that run on your own computer do not use your allowance. ## Region and availability Which models you can use also depends on the country of your billing address and, for some models, on age confirmation in your account. The live list is on the [model availability page](https://ai-game.dev/model-availability). The app's model picker shows the region your availability is based on and marks models that are not available there. ## Your other devices The app can make this computer reachable from your other computers and devices signed in to the same account, for example to follow a chat or approve a tool call from another machine. - In the desktop app: **Settings**, **Devices**. - In the CLI: `gamedev remote status`, `gamedev remote pair` and the other `remote` subcommands, or `/remote` in the interactive CLI. Pairing asks separately whether the other device may view chats, control them and use this computer's shared models. See [the CLI reference](https://ai-game.dev/docs/wiki/app/cli#remote) for every subcommand. The editor sessions and devices that hold an authorization for your account are listed on the Connected devices page of your account on ai-game.dev, where you can revoke them. ## Settings that belong to your account The desktop app's **Settings** window groups everything in one place: **General**, **Appearance**, **AI assistant**, **Voice**, **Permissions**, **MCP servers**, **Claude Plugins**, **Model storage**, **Devices**, **Privacy**, **Account** and **About**. **Account** shows your account and subscription; **Privacy** controls usage data, error reports and your anonymous ID. ## Next steps - [Open a project](https://ai-game.dev/docs/wiki/app/projects-and-engines) and connect your engine. - [Choose a model](https://ai-game.dev/docs/wiki/app/agents-and-models) for your first chat. - Problems signing in? See [Troubleshooting](https://ai-game.dev/docs/wiki/app/troubleshooting#sign-in). --- Source (HTML): https://ai-game.dev/docs/wiki/app/sign-in-and-account