AI and agents
How Flockbay’s agent works
Flockbay’s agent works in turns: you send a message, it calls tools in your project, and the reply ends with a receipt of every file it changed. How much it may do without asking is the chat’s permission mode.
Turns and steps
Each message you send starts a turn. While it runs, the reply updates in place, and every tool call is a step row in the thread that names what it touched: the node, the file, the command. Open a step to see what was sent and what came back, such as the command, its output and exit code, or the diff of a file.
Ctrl⌘+O switches the transcript view between Normal, Thinking and Verbose. A turn can also stop to ask you something; the question arrives as a card in the thread and the turn waits for your answer. Messages you send while a turn runs are queued and go next.
Build and Ask
The composer has two turn modes. Build changes the game. Ask reads, plans and reviews, and changes nothing, so it runs while another chat on the same game is building.
Several chats can build one game at once, each waiting for a file another is writing. When as many are building as can, this chat offers Ask now, or Queue Build turn, which starts when one of them ends.
Plan mode and permissions
The Permissions menu beside the model sets how much the agent may do in this chat without asking. Shift+Tab in the message box, or Ctrl⌘+Shift+M anywhere in the chat, steps through Plan mode, Ask before edits and Edit automatically; Full access is picked from the menu. Which modes a chat has depends on the AI it runs on.
| Mode | Without asking | It asks before | On |
|---|---|---|---|
| Plan mode | Reads the project and writes a plan | Any change: nothing changes until you press Build it | Claude Code |
| Ask before edits | Reads the project | Each edit and each command; on ChatGPT, each command that changes files | Every AI |
| Edit automatically | Edits this game’s files, and runs scripts in it, the Godot editor and Blender | Other commands, and edits outside the game | Claude Code |
| Game folder only | Runs commands, edits this game’s files and runs scripts; its commands change files only in this game’s folder and the home folder Flockbay gives its tools | Nothing | ChatGPT, Flockbay’s hosted models, an API key |
| Full access | Runs commands, and reads and edits files, anywhere on this computer | Nothing | Claude Code, ChatGPT |
Approving a step
When a mode asks, the question takes the place of the message box, and each answer is one press. Allow lets it run this once. Always allow stops the question for that kind of command in this game. Deny stops it, and the agent tries another way. Keys 1 to 9 press the row with that number, and words typed in the box tell the agent what to do instead.
A Claude Code edit asks Allow, Allow all edits in this chat or Deny, with the file’s diff; a ChatGPT file change asks Allow or Deny.

What no mode guarantees: Flockbay’s own tools run the game’s scripts, the Godot editor and Blender as your user, outside the agent’s sandbox, and a game script can do anything your user can. Only Full access lets the agent itself work anywhere on your computer, and Always allow takes away the question, not the risk. Keep the project in Git, and any change can be rolled back.
The brief comes first
For a new game, Flockbay starts with questions, one round at a time, each with a recommendation and a line of why. Then it writes a brief: what gets built first, what comes after, and what is not in this version. Nothing is built until you approve it.
An ask that is too big for one person gets the truth and a smaller first version, not a starter project dressed up as a yes. Every later turn is held against the brief you approved, which is kept in your project as GAME-BRIEF.md.
It writes real files in your project
Flockbay reads, creates and edits ordinary files in your project folder: scenes, GDScript and C# scripts, resources and assets, through the Godot editor when it is open. Every change through the editor is one step of Godot’s undo history, and the result is a Godot project any Godot editor opens.
It works by your AGENTS.md
If your game’s folder has an AGENTS.md, the agent follows it as your rules for the project: the conventions, folder layout, naming and the files not to touch, as you wrote them for Codex, Cursor or Claude Code. With no AGENTS.md, a CLAUDE.md in the folder is read instead. No message has to mention either file.
Chats on Claude Code read CLAUDE.md the way Claude Code does anywhere.
Reviewing what a turn changed
A turn that changed files ends with a receipt under its reply: "Changed 3 files +42 −7", then a row per file. Open a row for the file’s diff, Open to show it in the Godot editor (in the editor’s dock), and Revert to put back the file as it was before the turn.
Review changes, on the receipt, opens every file the turn changed in one scroll, in a pane beside the chat. Each hunk has Revert, each file Revert file, and ↑ and ↓ move between files. A hunk edited again since the turn is not reverted on its own: Revert file puts the whole file back. In a Git repository, Commit… opens the Version control panel with the reply’s first line as the message. Close, Ctrl⌘+\ in Flockbay’s window or Esc in the editor’s dock, goes back to the chat.
Revert this turn, on a turn’s receipt, takes back every file it changed, and Redo puts the changes back. A project in Git also shows every uncommitted change in the Version control panel’s Changes tab (Ctrl⌘+Shift+G).
It plays its own work
After it builds, Flockbay runs the game, headless or in the Game screen, sends it input events, reads stdout and the debugger, GDScript parse errors included, and captures the viewport. That is how a broken script, or a player who falls through the floor, gets caught before you press Play.
What you decide
Whether the game is good is yours to judge. Play it, and say what is wrong in the same chat: that is the normal loop, not a failure of the tool.
The editor stays yours too. Change anything by hand in the Godot editor, and Ctrl⌘+Z takes it back.
Flockbay runs on its hosted AI, free to start and the same on every plan, or on your own: the model you pick from the menu beside Send, among the models Claude Code offers your Claude account, your ChatGPT account’s models, or any model your API key reaches.
AppImage, x86_64. Ubuntu 22.04, Debian 12, Fedora 39 or newer.
Intel or AMD Chromebook, with Linux turned on.
See also: AI game maker that writes the code and AI game maker.
