Skip to content

A copilot for Godot, or something that does not need one

By Eduardo Orellana · Updated

A copilot for Godot suggests code while you type; Flockbay builds, runs and play-tests the game itself, and you can read or change every line of GDScript it writes. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building. It runs on Windows, macOS and Linux, on the official Godot engine.

AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.

Intel or AMD Chromebook, with Linux turned on.

Download for macOSDownload for WindowsDownload for Linux

What a copilot assumes about you

The whole design of a code copilot rests on one assumption: you can read the suggestion. It offers, you evaluate, you accept or you do not. The value comes from your ability to spot the wrong one in a second, which is a skill built over years.

Take that skill away and the tool inverts. A person who cannot read GDScript accepts everything, including the suggestion that quietly breaks something three files away. The suggestions get faster and the outcome gets worse. This is not a fault in the copilot. It is being used outside the assumption it was built on.

So the question is which of those two people you are, and the answer decides the category of tool, not the brand.

More on this: Making a Steam game with AI: what the platform actually requires

If you do write GDScript

Then a copilot in your editor is the right thing and you should use one. Autocomplete over a language you know is straightforwardly good, and there is no argument to be made against it here.

Flockbay is not competing for that job. It does not offer inline completions and it is not going to make you a faster typist. It is also not a plugin for a Godot you installed yourself: it ships its own copy of the Godot editor, with its chat in a dock. If what you want is your own coding agent with the running game under it, Claude Code, Codex or Cursor can connect to Flockbay over MCP, free for your first build.

If you do not

Then the useful move is not a faster way to produce code you cannot evaluate. It is to change what you are evaluating. Flockbay has it write the whole system — not a line, a system — as GDScript inside your Godot project, and then asks you to judge the thing you can actually judge: the game.

You describe what should happen. The wolves hunt at night, the door needs the key, the boat drifts if you let go of the oar. Flockbay writes it. You press play, the game runs locally on the copy of Godot bundled with the app, and you find out that the wolves are far too fast. You say so. It changes.

That is a complete loop for someone who cannot read the code, in a way accepting completions is not. You are never being asked to certify something you cannot see. You are being asked whether the game is right, which you can answer better than any model can.

More on this: Prompt to 3D game: questions first, then the world and the systems

A copilot stops at the script, and a game does not

A game is not only code. It is a world, and Flockbay starts a level above both. It asks what you are making, one round of questions at a time with a recommendation each, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it.

Then it builds the scenes as real nodes in the scene tree, as a 2D or 3D project, read from your description and confirmed before anything is created. In a 3D project that is the player controller, characters and props, with terrain, water, sky or weather from a Godot plugin when the game needs them. In a 2D one it is a TileMapLayer whose TileSet terrains give the edges and the collision, Parallax2D layers behind it, and sprites at an exact position, rotation and scale. Then it play-tests its own work: it runs the game headless or in a window, sends input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport.

Which means the split is roughly the opposite of a copilot's. A copilot writes the small pieces and leaves the structure to you. Here the structure, code and scenes, is handled, and you own the judgement. When a call is pure taste, where the crate sits or which way the path bends, Godot's own editor is there in the Standard and Full views, and Godot's undo takes a change back. A sentence gets you a layout; your hand can get you the exact layout.

More on this: Make a game with AI and no coding, without a closed toolbox

The practical facts

Flockbay is a desktop app for Windows, macOS and Linux that works with Godot 4.6+, with its own copy of Godot inside, so there is no separate engine install, and a project from another Godot version can stay on your own Godot of that version. Your project is a normal Godot project in a folder you own.

Building needs an internet connection since the chat and asset generation come over the network. Playing what you built does not. Free AI to start: Flockbay's AI and your own Claude, ChatGPT, agent or API key are free for your first build; after that, a plan keeps you building.

More on this: Vibe coding a game, and the part vibe coding is bad at

Questions

Is Flockbay a code copilot?
No. A copilot suggests lines to a programmer who evaluates them. Flockbay writes whole systems, builds the world, plays it to check, and you evaluate the game by playing it.
Does it work inside the Godot editor?
Yes, its own. Flockbay is a desktop app with the official Godot bundled inside, and opening a game opens the Godot editor with Flockbay's chat in a dock. It is not a plugin you add to a Godot install of your own.
Should I use a copilot instead?
If you write GDScript and want to write it faster, yes. This is for people who do not want to write it at all.
Can I read the generated code?
Yes. It is ordinary GDScript in your project. Nothing requires you to.
Where does the game run?
Locally on your machine, on the copy of Godot that ships with the app.

Free to download for Windows, macOS and Linux.

Download Flockbay free