# Quickstart: your existing Godot project

Open your project, have Flockbay explain its scenes, autoloads and main loop, ask for three small changes and pick one, then review the diff, run the game and revert the turn if it is wrong. Two prompts to copy.

Source: https://flockbay.com/docs/quickstart-existing-project/ · Updated 2026-11-01

## 1. Open your project

On Home, choose **Open project…** (Ctrl+O) and pick the folder that holds project.godot, or a folder above it. From PowerShell, `flockbay-desktop.exe --open-game <folder>` opens the same project: [Command line](/docs/command-line/).

For a project Flockbay did not make, a card lists what adding Flockbay writes before anything is written. **Add and open** opens the project in the Godot editor with the chat docked beside it. [Open your existing Godot project](/docs/open-an-existing-godot-project/) lists what the card adds and how to take it out again.

![Home’s Start panel: Open project… first, and the Godot projects on this computer beside it.](https://flockbay.com/docs-captures/install-on-windows-start.webp?v=32a390bbbf)

## 2. Have Flockbay explain the project

Switch the composer to **Ask** (Ctrl+Shift+A). An Ask turn reads and changes nothing. Paste this and press Enter. If the project has an AGENTS.md, the agent already has it.

```
Before you change anything, explain this project to me: the main scene and what it loads, every autoload and what it is for, and the scripts that run the main loop, each with its file and the functions that matter. Then list anything that looks broken or unfinished. Change no files.
```

![Flockbay’s chat docked in the Godot editor: the thread, and under it the message box with the model, Demo, and the mode, Build.](https://flockbay.com/docs-captures/the-editor-chat-dock.webp?v=b7ad34d303)

## 3. Ask for three small changes, and pick one

Still in Ask, send this. Then switch to **Build** (Ctrl+Shift+A) and answer with the one you want, such as "Make the second one."

Each tool call is a step in the thread that names the file or node it touched. Open a step to see what was sent and what came back: the diff of a script, or a headless run’s output and exit code.

```
Suggest three small, safe changes to this project that I can check in under a minute each. For each one: what changes, the file and node it touches, and how I will see it when I press Play. Make none of them yet.
```

![A turn’s steps, one open to the diff of the script it wrote, then a headless run that exited 1.](https://flockbay.com/docs-captures/asking-for-a-change-steps.webp?v=a13fa24e5e)

## 4. Review the diff, run it, and revert if it is wrong

The turn ends with a receipt, such as "Changed 2 files +41 −6", and a row per file. Open a row for its diff, or press **Review changes** to read every file in one scroll; Ctrl+\ closes it in Flockbay’s window. A line under a file says what the agent’s own headless run printed, a parse error with its file and line included.

Press F5 to play the main scene, or F6 for the open scene, and F8 to stop. **Revert** on a row puts that file back as it was before the turn, and **Revert this turn** puts back every file the turn changed. In a Git repository, the Version control panel (Ctrl+Shift+G) shows the same changes for you to commit.

![A turn’s receipt: Changed 2 files, Review changes, Revert this turn, and the parse error a headless run printed.](https://flockbay.com/docs-captures/asking-for-a-change-receipt.webp?v=aa19a1f1d0)

Related: [Open your existing Godot project](/docs/open-an-existing-godot-project/), [How Flockbay’s agent works](/docs/what-director-1-does/), [Keyboard shortcuts](/docs/keyboard-shortcuts/)