Connect Godot

Godot setup is simpler than Unity because Godot’s project files are plain text. Forge parses .tscn, .gd, and project.godot directly off disk. There’s no TCP bridge to install, no UPM package, no Editor extension.

What you do

1. Open the project folder in Forge. Mode dropdown, Open project, pick the folder. If project.godot is in the root, Godot mode auto-enables and a Godot pill appears in the title bar.

2. Point Forge at your Godot binary so build tasks can run. Settings → Workspace → Godot binary, browse to your godot.exe (or godot4.exe, or wherever your Godot 4.x install lives). Forge remembers it across sessions.

   You can also use the GODOT environment variable if you’d rather not pin it in settings.

That’s it. The Inspector grows Scene and Outline tabs, skills tagged for Godot fire when their version matches, and tasks that reference $env:GODOT resolve correctly.

What’s available

• Scene tab parses .tscn files and renders the node tree. Click a script-bearing node to open the script in Monaco. See Scene tree inspector.
• Outline tab parses the active .gd file’s class members, exports, methods, and signals. See GDScript outline.
• Build tasks can use $env:GODOT to drive headless exports. See Build mode.

What’s not (yet)

• No live editor connection. Selections in Forge don’t ping the running Godot Editor and vice versa. Each side reads the file system independently.
• No write tools equivalent to Unity’s create_gameobject and friends. Code edits go through the regular diff review flow, and scene edits happen by editing the .tscn file directly (which the agent can also do, with diff review).

A live editor bridge is on our roadmap. Until then, the file-based approach covers the common cases without needing the Godot Editor to be running at all.

Common issues

No Godot pill in the title bar. Forge didn’t find project.godot in the project root. Check that the file actually exists at the top level of the folder you opened.

Tasks fail with '$env:GODOT' is not recognized. The Godot binary path isn’t set. Open Settings → Workspace → Godot binary and pick the executable.

Scene tab is empty. The active workspace tab isn’t a .tscn file. Click a .tscn in the project explorer and the Scene tab populates.

Outline tab is empty. The active workspace tab isn’t a .gd file. The Outline tab only fires for GDScript.