GGua REFERENCE日本語GitHub ↗
TOOL / INSPECTOR

Inspector

Inspect a running game's semantic UI tree, node state, logs, and screenshots. Inspector is the first tool to reach for when validating an integration.

Run and connect

  1. Install repository dependencies
    PowerShellpowershell
    bun install --frozen-lockfile
  2. Start browser Inspector
    Terminal 1powershell
    bun run --filter @gua/inspector dev
  3. Start the in-game bridge

    The Godot sample starts its bridge inside the game process. Use the sample bridge when you only need to exercise the protocol.

    Terminal 2 (sample bridge)powershell
    bun run bridge:ws
  4. Connect to the URL
    texttext
    ws://127.0.0.1:8765

What to inspect

Semantic UI Tree

Screen, role, ID, text, and parent/child structure. Confirm that the expected Controls were collected.

Node state

Visibility, enabled state, focus, checked state, value, and bounds used by tests.

Logs

Runtime logs published by the game, useful for state changes the connection alone cannot explain.

Screenshot

An explicitly published PNG for comparing semantic state with the rendered frame.

Desktop development build

Running the Tauri shell from source also requires the Rust toolchain.

PowerShellpowershell
bun run --filter @gua/inspector build
bun run --filter @gua/inspector tauri:dev