Engine Status Dot

The colored dot in the AI chat header tells you the live state of the engine bridge at a glance. Click it to see detailed engine information or get setup instructions.

Connection states

The dot changes color based on the bridge connection state:

  • ● Green (connected) — The bridge is live. Bridge commands execute in real-time inside your Unity or Godot editor.
  • ● Yellow (connecting) — The bridge is starting up, reconnecting, or waiting for scripts to finish compiling.
  • ● Red (disconnected) — The bridge is not reachable. Click the dot to see the error and retry options.
  • ● Gray (no engine) — No game project is open in the current workspace. See No engine detected below.

The info card

Clicking the dot opens an info card with live details about the connected engine:

  • Engine — Unity or Godot, with version number
  • Project — The name of the open game project
  • Status — Current bridge connection state
  • Game folder — The path EngineForge is targeting

The card closes when you click outside it or press Escape.

No engine detected

When the dot is gray it means EngineForge could not find a Unity or Godot project in the current workspace. Common reasons:

  • You opened a folder that is not a game project (e.g. a backend repo)
  • You opened a parent folder and the game project is a subfolder — EngineForge auto-detects one level deep, but you may need to confirm the target. See Game Folder.
  • The project is missing its detection file (ProjectSettings/ProjectVersion.txt for Unity, project.godot for Godot)

Clicking the gray dot opens a setup card with step-by-step instructions for connecting the bridge for your engine.

Bridge limitations

  • Unity: The bridge cannot execute commands while the editor is in Play mode. Exit Play mode first.
  • Godot: The bridge cannot execute commands while a scene is running. Stop the scene first.
  • Commands that create or modify assets trigger an asset database refresh, which can take a few seconds in large projects.