Is there a Flockbay command line?

Not as a binary of its own. Building a game in Flockbay happens in the app: a desktop application for Windows and Linux, with the Godot editor in it and the chat in a dock. You approve a brief, and Flockbay builds the world, writes the GDScript and play-tests the result. There is no flockbay command that makes a level or runs a build.

If your working day lives in a terminal, the way in is your own agent. Claude Code, Codex or any MCP client connects to the app's MCP server, flockbay-stage, while the app is open with your game. Its tool calls reach the same world tools Flockbay's AI uses (terrain, water, sky, weather, the player controller, props), the open Godot editor, and the running game: Play, a headless run, timed input events, viewport captures, stdout and the debugger. The agent loop is yours, on your own model.

For someone who does not write code at all, none of that matters. The chat in the app is the whole interface, and there is no reason to open a terminal.

More on this: Connect your own agent

A project directory. The engine underneath Flockbay is Godot, which is open source, and what you build is a real Godot project: ordinary files, in ordinary folders, in a documented format.

That is the part people usually want a CLI for. Backing the project up, copying it to another machine, putting it in version control, handing it to somebody who does write code, or opening it in Godot directly. None of those need a command from us, because none of them are special. They are file operations on files.

It also means nothing about your project is locked behind a tool that has to still exist. A directory of Godot files is readable by an engine anybody can download for free.

More on this: Flockbay vs Summer Engine: official Godot, or an engine built on it

Flockbay writes GDScript into your project, and so does your own agent if you connect one. Those are text files sitting in the project directory with everything else. You are never asked to open them, and nothing hides them from you.

This is worth knowing if you have any technical background at all, or if you might work with somebody who does. A programmer looking at your project sees a normal Godot project with normal scripts in it, not an exported blob or a proprietary bundle. Handing the work over is a handover rather than a migration.

The reverse is also true: files you put into the project, whether models, textures, audio or your own scripts, are read the way Godot reads them.

Building. The chat, asset generation and world data all come over the network and run through the application, which is also why an internet connection is required to build. Your own agent works through the app too: the MCP server is served by the app while it is open with your game, so there is no path that builds without it.

Playing is different. The game runs locally on the copy of Godot bundled with the app, on your machine, at your framerate, and it does not need a connection.

If you were hoping to automate world building from a script, the honest answer is: through an agent, yes; through a shell script, no. Your agent's tool calls can sculpt terrain, lay water and place props in a Flockbay world, and it can run the game headless to check them. What it cannot replace is the person who plays the result and says whether it is right.

More on this: Summer Engine vs Ziva vs Flockbay: which Godot AI tool to pick in 2026

64-bit Windows 11 and Linux (an x86_64 AppImage), with an earlier Mac build, as a download. No phone version.

Free to install, and the AI is free. Flockbay is free, AI included: free hosted AI every day, or your Claude or ChatGPT plan, your own agent, or an API key.

None of the above is required. Plenty of people building here will never open a terminal, never hand the project to anybody, and never need to know where the files sit on disk. The point is only that the option exists, that it costs nothing to keep open, and that it is there because the project is stored in a format somebody else already documented rather than one we invented.

Plenty of non-technical creators work with somebody who is not. A friend who programs, a contractor for the last ten percent, an artist with a technical streak.

The arrangement that works is that they open the project in Godot, or point their own agent at it, and work the way they normally would, while you continue in Flockbay, asking for world and behaviour and judging the result. Nothing about the project format prevents this, because there is no proprietary layer between the app and the files.

What is worth agreeing up front is who owns which files, since two people editing the same scene at once ends the way it always does.

The other thing that helps is deciding early which parts are theirs permanently. A programmer who owns the systems and a creator who owns the world is a clean division. A programmer who is called in to fix things intermittently ends up rewriting whatever changed since last time.