Browser games

BIGGI can manage a local dev server and an isolated browser page for supported JavaScript and TypeScript game projects.

It detects common projects built with Phaser, Three.js, Babylon.js, PixiJS, Excalibur, Kaplay, Matter.js, and compatible custom Canvas or WebGL code.

Before you start

  1. Open the game repository in VS Code.
  2. Install the project dependencies.
  3. Provide a conventional dev, start, or serve script.
  4. Install a compatible browser. BIGGI uses an installed browser and does not download one during an ordinary Game Loop task.
  5. Select Gameplay, Tech Art, Perf, Debug, or Code.

If automatic discovery is wrong, configure the browser-game command, URL, or executable in biggi.jsonc.

What BIGGI can do

  • Start and stop the dev server
  • Open an isolated game page
  • Read browser console output and runtime errors
  • Capture screenshots
  • Run project tests and production builds
  • Execute input-driven playtest scenarios
  • Inspect opted-in scene and runtime state
  • Profile renderer, network, and main-thread behavior where the browser exposes it
  • Compare bounded evidence from a passing and failing run

BIGGI edits browser-game scenes through normal source files. It does not provide an unrestricted live scene editor.

Ask for verification

Use the Gameplay agent. Fix the jump so holding Space does not create repeated mid-air jumps. Inspect the input loop first, make the smallest change, then run the game and verify the behavior with a focused browser playtest.

For performance:

Use the Perf agent. Profile the first 10 seconds of the main scene, identify one repeatable long task or renderer bottleneck, make a bounded fix, and compare the before and after evidence.

Deeper runtime state

Basic running, console, screenshots, tests, and builds are usually zero-config. Deeper framework trees and project-defined state or actions require the optional BIGGI game contract to be connected at the application entry point.

Ask BIGGI to initialize the game contract when you need semantic runtime queries or repeatable project actions. Review the generated source changes before keeping them.

Browser differences

Chromium provides the deepest profiling and emulated CPU or network conditions. Firefox and WebKit can run supported functional workflows but may report profiling or throttling operations as capability gaps.

When an operation is unavailable

  • Run the project's dev command manually to resolve dependency or startup errors.
  • Confirm BIGGI detected the correct URL.
  • Configure the browser executable if Chrome or Chromium is not discoverable.
  • Use Chromium for deep profiling.
  • Add the game contract only when you need application-specific runtime state.