Godot workflow
EngineForge is the AI platform for game development, with Godot support built in. Start a new Godot game with the engine set up for you, or open your own Godot 4.0+ project. The Crew works across scripts, scenes, editor state and the running game, then exports desktop builds.
Managed Godot
EngineForge downloads the official Godot build, checks it is genuine, installs it, keeps it running and opens your game in the Cockpit with a Scene view, Play and Stop. If the same Godot version is already on your computer, EngineForge uses it instead of downloading again.
Godot 4.6.1 on macOS and Windows. Managed games use GDScript and the Compatibility renderer.
How Managed Godot works →
Export Game
Export desktop builds for macOS, Windows, Linux with your game's name, icon and version. Each build reports what was checked, and your project is never changed.
For Godot 4.6.1 projects, managed or in your own editor. No store publishing or signing of exported games.
Export a game →
Project context
EngineForge indexes the project on your computer and reads the Godot editor directly: scenes, nodes, signals, resources and how they connect.
EngineForge context model
Relationships relevant to the current task
Godot capabilities
The Crew reads the project in Godot, makes changes in the editor, and runs the game to check them.
Inspect, create and change scenes and the node tree.
Work with properties, signals, groups, references and resources.
Paint and edit TileMap and TileMapLayer layers and cells.
Use editor actions, run the game, and watch what happens while it plays.
These are capability families, not a complete command catalog. See the Godot integration docs for current capability coverage and limitations.
From scene context to running behavior
From understanding the project to a change in Godot, then a run of the game when the change affects how it plays.
New or existing
Start a managed game, or open the Godot project already on disk.
Godot context
Read the nodes, signals, resources and editor state the task touches.
Godot action
Change the scenes, nodes and settings the task needs, inside the Godot editor.
Your call
Try it yourself, or send the Playtester to play it in its own window.
When observable
Observe the named condition instead of assuming the code is enough.
Developer decision
Inspect the change, diff, and relevant runtime evidence.
Not every task needs every stage. This is one possible path using only the context, actions, and verification relevant to the work—not a fixed autonomous pipeline.
A real Godot example
In an evidence-backed Godot platformer scenario, the collection logic existed in the scripts, but the scene was missing the signal connection needed to update the counter.
Read the first-hand workflow →Observed problem
Coin collected
Counter unchanged
Scene finding
Logic present
Signal connection missing
Change
Restore the scene connection
Valid observation
Coin disappears and counter updates
The developer reviews the scene change and what the run showed. This checks the coin counter, not the whole game.
Crew inside the workflow
Maestro leads the session and brings in Builder, Juicer, Systems Smith or Playtester as the Godot task needs. Plan mode stays read-only; Forge lets each specialist use the tools of its role within your approval settings.
Explore EngineForge Crew →Inspectable work
Everything the Crew does in your Godot project stays available to review: the changes, the evidence, and your decision.
Change
Inspect the project changes produced during the task.
Evidence
Review the logs and what was seen in the running game.
Review
Keep approvals and file checkpoints visible.
Godot support and boundaries
Available now
Godot 4.0 or later in your own editor, or Godot 4.6.1 managed by EngineForge for new games, alongside Unity.
Capability scope
The Crew can do what the Godot integration supports, and no more. Managed games use GDScript and the Compatibility renderer.
Exact coverage
The Godot integration docs list exactly what is supported today, with setup steps and limits.
Continue with Godot
Explore the integration, read the first-hand workflow, or download EngineForge.
Read the first-hand workflow →