VS CODE CONNECTED

The engine is in the room.

Chat, engine tools, permissions, snapshots, diffs, and parallel agents share one workspace-aware runtime—without turning your editor into a dashboard.

Install for VS Code Read the docs

EnemySpawner.cs — DungeonCrawl

12public class EnemySpawner : MonoBehaviour
13{
14    [SerializeField] private Enemy enemyPrefab;
15    [SerializeField] private Transform[] points;
16
17    public void SpawnWave()
18    {
19        foreach (var point in points)
20            Instantiate(enemyPrefab, point.position, point.rotation);
21    }
22}

BIGGI — /gameplayUnity 6 · C#

the second enemy wave never appears

The script is fine. enemyPrefab was unassigned on Spawner in Level2.

✓ game_scene_edit · wired▸

✓ game_playtest · passed▸

verified · frame 612

Ask BIGGI…

ENGINE DETECTIONGAME LOOP TOOLSWORKTREE ISOLATIONREVIEWABLE EVIDENCE

The Game Loop

Run the game from the conversation

Engine actions appear as first-class, reviewable tools. BIGGI can read the real console, query a scene, repair a serialized reference, replay the failure, and attach the evidence without asking you to shuttle errors between windows.

Unity editor bridge and Godot runner selected automatically
Static and live scene queries with root-cause hints
Tests, screenshots, profiling, and playtests rendered in chat

BIGGI Game Loop — Dread Crown playtest

Agent Manager

Explore several implementations safely

Start independent tasks or ask for up to four versions of the same idea. Each worktree has its own session, branch, terminal, live diff, permissions, and model.

Parallel worktrees keep experiments off your working branch
Compare models or approaches against the same prompt
Apply selected files locally, merge, or open a pull request

Agents

Review and recover

Every change leaves a trail

Open the diff attached to a message, inspect unified or split views, and use Git-backed snapshots when you need to return to an earlier state.

Line-level diffs tied to the message that caused them
Granular Allow, Ask, or Deny permissions per tool
Snapshots make agent changes reversible from chat

Review changes

4141 func _physics_process(delta):
42−    var dir = Input.get_vector("left", "right", "up", "down")
43−    velocity = dir * SPEED
44−    move_and_slide()
45−
46−func _input(event):
47−    pass
42+    var dir = Input.get_vector("left", "right", "up", "down")
43+    velocity = dash_dir * DASH_SPEED if dashing else dir * SPEED
44+    move_and_slide()
45+
46+func start_dash(dir: Vector2):
47+    dashing = true
48+    dash_dir = dir
49+    cooldown.start(DASH_COOLDOWN)
50+    dash_started.emit()

VS Code field notes

Before you install.

Does the Game Loop run inside VS Code?

Yes. The extension talks to the same local BIGGI runtime as the CLI. Unity work uses the running editor bridge when available, while Godot can run headlessly or capture a windowed screenshot when the task needs visual evidence.

How do parallel agents avoid overwriting each other?

Agent Manager can put every task or alternative version in its own git worktree. You review each live diff and decide whether to apply files locally, merge the branch, or open a pull request.

Do I have to use the BIGGI gateway?

No. Use provider keys you already have or a supported local model. The extension and Game Loop work the same way either way.

Does it work in VS Code-compatible editors?

BIGGI targets standard VS Code APIs and supports VSCodium. Other forks can vary when they restrict extension APIs or marketplace installation.

EXTENSION READY

Put the running game beside the code.

Open your Unity or Godot project and give BIGGI a mechanic to prove.

Install for VS Code