Looking for a Cursor for Godot

The phrase describes something specific: an editor where an AI reads your project, suggests code inline, and applies multi-file edits on request. People searching it usually already program, already use Godot, and want the same assistance they get in a web codebase.

Stage Engine is not that thing, and saying otherwise would waste your afternoon. It is not a plugin, it does not attach to your existing Godot editor install, and it does not sit in your keybindings offering completions while you type.

What it shares with the idea is the important part: an AI that writes GDScript inside a real Godot project, with the project structure and the code as the working material rather than a proprietary format.

A desktop application for Mac and Windows that ships with its own copy of Godot. Inside it there are two surfaces. A builder, where you place terrain, water, weather, buildings and characters with your hands. And Director 1, which writes the code for the behaviour you ask for, into the project, where you can read it.

The output is a Godot project. Not an export, not a bundle, not a save file with a custom extension. That is the property that matters if you are coming at this from a developer direction, because it means nothing you build here is stranded.

The game runs locally when you press play, on the bundled Godot, using your machine. There is no streaming and no browser preview.

It fits someone who wants a game and does not want to write the code, including people who could write the code and have decided their time is better spent on the world and the feel. The loop is: ask for behaviour, play the result, say what is wrong, repeat. Being able to read GDScript makes that loop faster but is not required at any point.

It does not fit someone who wants to keep their existing editor, their existing project layout, and their existing workflow, and just add AI to it. That is a plugin-shaped want and Stage Engine is app-shaped. If you have a large Godot project you are happy with, a general AI coding tool pointed at that repository is the more sensible answer and we would rather you did that than fought this.

There is a middle path worth knowing about. Stage Engine can be driven by an external agent over MCP, so if you already work with your own AI tooling you can point it at the app rather than switching to Director 1 for everything. That keeps your existing habits and your existing model choice.

This is the one place where a developer-shaped workflow and this app meet cleanly. It is not the main path and it is not required; most people use Director 1 and never think about it.

Free to download for Mac and Windows, with a free plan. Indie is $10 a month and Pro is $50. Those buy more usage, not more engine and not more features.

Building needs an internet connection, because Director 1, asset generation and world data come over the network. Running what you built does not.

The reason is that most of what makes AI unreliable in a game project is not the model, it is the ambiguity around it. A bare project gives an agent no idea where things belong, what a scene means, or how the world is put together, so it infers, and inference is where the expensive mistakes come from.

Owning the app means owning that structure. The project layout, the builder, the way the world is represented and the way work is expressed to the agent are all one thing, and the code that comes out lands correctly far more often as a result.

A plugin cannot do that, because it inherits whatever the surrounding project already is. That is the trade: less flexibility about your existing setup, considerably more reliability inside this one.