# The New AI Game Dev CLI: A Terminal UI Built for Game Developers

The gamedev CLI has a new terminal UI with a 3D logo intro, a composer pinned to the bottom, live tool calls and a clean redraw on every resize.

_Last updated: 2026-11-19_

The AI Game Dev CLI, the gamedev command, has a completely new terminal UI. It opens with a rotating 3D logo, keeps the message box and the status line pinned to the bottom of the window at any size, shows every tool call live with its own timer, and redraws cleanly when you resize the terminal. Nothing about how you work changed: the same agent, the same commands and the same projects. It is simply a much nicer place to spend a day of game development.

This post is a short tour of the new CLI terminal UI, with animations recorded from the real app, and a few notes on how we got there.

## What the Old CLI Looked Like

The CLI has always been the fastest way to talk to the AI Game Dev agent from a game project: run gamedev in a Unity, Unreal Engine or Godot project folder, describe what you want, and the agent reads the project, edits files and drives the editor. But the screen it gave you was plain. A welcome line sat at the top, the message box followed it wherever the conversation went, and the status line was a row of bracketed key names in mixed colors.

[Media: Before: the previous CLI start screen.]

It worked, but it did not feel like a tool you would want to keep open all day next to the editor. We wanted it to feel as polished as the best agent terminals, and to look like ai-game.dev.

## A 3D Logo Intro, Drawn in the Terminal

When gamedev starts now, it first clears the screen and its scrollback, so the app opens on a clean screen instead of under whatever your shell printed before. Then the AI Game Dev "A" turns into place in 3D while the AI GAME DEV wordmark types itself in beside it.

[Media: The new intro: a rotating 3D logo, rendered in the terminal with no images or fonts.]

There are no images or special fonts involved. The logo is a small 3D model that the CLI renders itself, frame by frame, into ordinary terminal characters with true color shading. The spin-in lasts under two and a half seconds. After that the logo only catches a short highlight now and then on the empty welcome screen, and nothing animates once you are working. On a terminal without true color it falls back to the 256-color palette, and the colors throughout the UI now come from the same palette as the ai-game.dev site.

While the logo is still turning, the message box is already there and already accepts input, so the intro never makes you wait.

## The Message Box Stays at the Bottom

The biggest change you notice after a few minutes is the layout. The message box, which we call the composer, and the two status lines under it are pinned to the bottom of the window, on every screen and at every window height. The conversation grows upward above them, the way it does in a chat app. Your eyes always go to the same place to type, and the important facts are always in the same place to read.

The status line shows the permission mode, the model, the active agent, how full the context is and your plan usage as a percentage. The second line lists the shortcuts that matter right now: ctrl+c to exit, shift+tab to change the permission mode, ctrl+o for details and space or ctrl+g for voice input, and on the right, the project folder. While the agent works, the first hint becomes esc stop, and the composer tells you that you can already type a follow-up, which is queued for the next turn.

[Media: A chat turn. These recordings use a scripted stand-in instead of a model, so they are the same on every run.]

## Tool Calls You Can Follow

Game development with an AI agent is mostly tool calls: reading scripts, running a build, changing a scene, calling the editor through MCP. The new UI gives each tool call its own row with the tool name, what it is doing and a live timer. When it finishes, the spinner turns into a check mark and the first line of the output appears underneath, so you can see at a glance what happened without opening anything.

[Media: A tool call: live timer while it runs, a check mark and its output when it is done.]

Long turns stay readable too. Finished steps collapse into a short list, and ctrl+o expands the steps of the current turn when you want the full detail.

## Slash Commands and the Model Picker

Type a slash and the command palette opens right above the composer: every command with a one-line description, filtered as you type, with tab to complete and enter to run. It is the quickest way to discover what the CLI can do, from installing the engine plugin and extensions to opening the editor or running a game.

[Media: The slash command palette, filtered as you type.]

The /model picker got the same treatment. Models are grouped by provider, each with a cost bar and a capability bar, so choosing between a fast cheap model and a deep reasoning one is a glance instead of a guess. The picker also tells you which models are available in your region and that the choice applies from the next turn. Every overlay in the CLI, from the model picker to /config and the MCP and plugin lists, now shares the same frame, the same keys and the same hint row.

[Media: The model picker: providers, cost and capability side by side.]

## Any Window Size, Any Resize

Terminal apps are often at their worst when you resize the window: half-drawn frames, a logo smeared across the scrollback, a message box stranded in the middle of the screen. We treated resizing as a first-class feature. When the window size settles, the CLI redraws the whole screen for the new size, and every screen keeps its composer at the bottom.

Small windows get a compact layout instead of a broken one. In a narrow terminal the logo shrinks and the welcome text moves under it; in a wide one the wordmark sits next to the logo. The status line drops less important items first, so the permission mode, the model and your usage stay visible even at 60 columns.

[Media: The same start screen in a 60x20 and a 130x40 terminal.]

## How We Built the New CLI Terminal UI

We built the new UI with AI agents, in a loop. One agent changed the UI. A small jury of two AI reviewers from different labs then looked at fresh terminal screenshots and recordings of every screen, side by side with screenshots of other popular AI coding terminals, and scored each screen on layout, readability, color, motion and behavior on resize. Anything below 9 out of 10 went back to the developer agent with the jury's notes. The screenshots in this post come from the same harness, which drives the real CLI in a terminal at many window sizes.

Between the jury and the code review that follows every change, the loop caught things a quick look easily misses: a logo smeared into the scrollback after a resize, a /config screen that did not fit an 80 by 18 window, a key hint shown while it could not work. The full test suite of the CLI runs on Linux, macOS and Windows on every change.

## Try It

The new CLI is available now. Install it from npm, or update the one you have, and run it in a game project folder:

```bash
npm install -g @baizor/gamedev
cd MyUnityProject
gamedev
```

On first launch, sign in with your ai-game.dev account. The full list of commands and flags is in the CLI reference at ai-game.dev/docs/wiki/app/cli, and if you are new to AI Game Dev, the quickstart at ai-game.dev/docs/quickstart walks you through connecting your engine. We would love to hear what you think of the new terminal, and what you want it to do next.

## Related

- AI Game Dev CLI reference: https://ai-game.dev/docs/wiki/app/cli
- Install AI Game Dev: https://ai-game.dev/docs/wiki/app/installation
- CLI for AI agents, up to 83% fewer tokens: https://ai-game.dev/blog/cli-for-ai-agents-fewer-tokens
- Quickstart guide: https://ai-game.dev/docs/quickstart

---

Source (HTML): https://ai-game.dev/blog/new-gamedev-cli-terminal-ui
