# An AI agent that works inside a Godot project

A Godot AI agent is an AI that works inside your Godot project instead of beside it: it edits scenes and GDScript, runs the game, reads the errors and plays it to check its work. Flockbay is one, and it is free: it builds and play-tests a whole Godot game on free AI every day or your own Claude or ChatGPT, on the official Godot engine, and it hands the same tools to Claude Code, Codex or Cursor over MCP.

Source: https://flockbay.com/godot-ai-agent/ · Updated 2026-10-13

## What an agent needs that a chat window does not have

The difference between an assistant and an agent is not the model. It is the surface. An assistant answers about your project. An agent acts on it — it can look at the world, change files, and see whether the change worked.

For a game, that surface has to include the world itself. Reading the scripts is not enough, because most of what a game is lives in the scene: what is placed where, how the ground is shaped or which cells of it are ground at all, what a character is standing on. An agent that can only read text is reconstructing the world from a shadow of it.

Flockbay works against a world it can actually address, and which world that is depends on the answer given when the project was made: 2D or 3D, with the answer read from your description of the game and yours to change. In a 3D project it is terrain, water, weather, buildings and characters. In a flat one it is the tile ground and the coverage the tiles are derived from, the band of scenery on the horizon, every sprite placed in the scene, and a character body whose feel is a set of named numbers rather than a script to be rewritten. Either way these are things it can reason about directly rather than infer from a folder of scripts, and that is the difference between an agent that composes reliably and one that produces confident nonsense.

## It agrees a brief, builds the game, and plays it before you do

Flockbay starts with questions, one round at a time, each with a recommendation, and writes a brief: what gets built first, what comes after, what is not in this version. Nothing is built until you approve it. Ask for a game like GTA 6 and you get the truth and a smaller first version, not a starter scene and a yes.

Then it builds. The world comes from world tools for terrain, water, sky, weather, plants, the player controller, characters and props, as real nodes and resources in the scene tree. The behaviour comes as GDScript: the door needs a key, the wolves hunt at night, falling in the river costs you a life. The code is visible. You are not asked to read it, and nothing stops you.

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. A jump that never leaves the ground reaches the agent before it reaches you.

What it does not do is [decide whether the game is good](/blog/how-to-judge-a-game-you-did-not-code/). You play it and say. That handoff is the normal loop, not a failure of the agent. And when the call is pure taste, the same world tools are buttons around the Godot editor’s own 3D and 2D view, so you can nudge the hill or repaint the path yourself, with Godot’s undo behind you. [Taste does not always compress into a prompt](/blog/when-to-stop-prompting-and-start-building/): a sentence gets you a valley; your hand can get you the exact valley.

## Running locally, on a real project

Flockbay is a desktop app for Windows, macOS and Linux, with the official Godot inside it. The agent is operating on files on your disk, in a real Godot project, and when you press play the game runs on your machine at your framerate. Nothing is streamed and nothing is rendered elsewhere.

That matters for an agent specifically, because the feedback loop is short. It writes, runs the game locally, reads the error, fixes it, and runs it again before you ever press Play. A round trip through [someone else's render queue](/blog/why-browser-ai-game-makers-hit-a-ceiling/) would make that loop slow enough to stop being a loop.

Building [does need an internet connection](/answers/does-flockbay-work-offline/), since the chat, asset generation and world data all come over the network. Playing the result does not.

## Your own agent, if you prefer

Flockbay exposes its capabilities over MCP, through one server, flockbay-stage, which means you are not required to use Flockbay's own AI as the only agent in the loop. If you already work in Claude Code, Codex, Cursor or another MCP client, it gets the same surface: the world tools, edits through the open Godot editor with undo, and the running game to play-test. In the app, Connectors, then Connect your agent (MCP), then Set up writes the line to paste. Connecting your own agent over MCP is free.

The point of that is not novelty. It is that the valuable part is the capability layer — the fact that the world is legible and operable at all — rather than any particular model. If the layer is right, a cheaper model composes reliably against it.

The download is free and so is building with it. [Flockbay is free, AI included](/answers/what-does-flockbay-cost/): free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

## Questions

### What is Flockbay?

A free AI game maker built on Godot. Its AI, also called Flockbay, agrees a brief with you, then builds the world, writes the GDScript into your Godot project and plays the game to check it, and revises it when you say what is wrong.

### Does the agent build the world too?

Yes. From the brief you approved, it builds terrain, water, sky, weather, plants, the player controller and props with world tools, as real nodes in the scene tree. The same tools are buttons in the Godot editor if you want to make a taste call by hand.

### Can I use my own agent instead?

Yes. Flockbay exposes its capabilities over MCP, so your own agent can drive them. Connecting your own agent is free. You pay your agent's provider for the model; Flockbay charges nothing for the connection.

### Where does the code end up?

In your Godot project, as ordinary GDScript, in a folder on your disk.

### Does any of this run in the cloud?

The AI and world data come over the network while you build. The game itself runs locally on the bundled Godot.

Download Flockbay free: Free to download for Windows, macOS and Linux. https://flockbay.com/

Related: [Claude or ChatGPT with Godot](/claude-or-chatgpt-for-godot/), [Godot AI](/godot-ai/), [Godot AI over MCP](/godot-ai-mcp/), [Godot copilot](/godot-copilot/), [Cursor for Godot](/cursor-for-godot/), [Flockbay for AI](/for-ai/)