Inspector — Remote Diagnostics & Live REPL for Xbox Homebrew

Status

🚧 Under development. Protocol handling, scan logic, and REPL command forwarding are stubs on the XBVault side. The Xbox-side native library (xb-inspector) has full architecture defined and is under active implementation at uwp-xray-depot. UI shell, console, font controls, and state management are complete.

The Problem

Developing UWP apps for Xbox Dev Mode means flying blind.

• No console you can actually see. OutputDebugString is invisible without a debugger. Console.WriteLine goes nowhere.
• Remote debugging ties you to Visual Studio. Attach, wait, hope it doesn’t crash. One bad deploy and you’re restarting the whole chain.
• Crash at startup? Zero diagnostics unless you set up ETW tracing — which requires yet another tool.
• Runtime state is a black box. Launch your app, stare at the TV, guess what’s happening inside. Did the asset bundle load? Is the config valid? Is the audio thread starving?
• Every iteration is slow. Deploy → launch → fail → guess → fix → repeat. No feedback loop.

This is the reality today. Mobile developers have adb logcat. iOS devs have device logs. Xbox homebrew devs have… nothing.

The Solution: xb-inspector

XB-Inspector is a remote diagnostics suite for Xbox homebrew. Drop in the library, and your app gets:

The library is designed for C++ primarily, with C# (MoonSharp) and Rust (mlua) flavors sharing the same JSON protocol.

What it is NOT

• Not a file transfer tool (File Explorer via SFTP already covers this)
• Not a replacement for breakpoints/step-through (keep Visual Studio for that)
• Not a crash reporter (separate system)
• Not compiled into release builds (#ifdef XB_INSPECTOR_ENABLED guard)
• Not a replacement for Xbox Device Portal (deploy still goes through WDP)

It sits in the gap between those tools — the live insight layer that mobile developers take for granted and Xbox developers don’t have.

Architecture

flowchart TB
    subgraph Network["LOCAL NETWORK (TCP/IP)"]
        direction LR

        subgraph Xbox["Xbox Series S/X<br/>Dev Mode UWP"]
            App["Homebrew App"]
            InspectorLib["xb-inspector library"]
            LogSink["spdlog"]
            LuaVM["Lua 5.4"]
            Sockets["xray-sock TCP"]
        end

        subgraph PC["Dev PC<br/>XB Homebrew Vault"]
            InspectorTab["Inspector Tab"]
            Console["Console<br/>(Log Feed)"]
            REPL["REPL Input"]
            StateWatch["State Watch<br/>(future)"]
        end

        App --- InspectorLib
        InspectorLib --- LogSink
        InspectorLib --- LuaVM
        InspectorLib --- Sockets

        Sockets <-->|"TCP / JSON"| InspectorTab
        InspectorTab --- Console
        InspectorTab --- REPL
        InspectorTab --- StateWatch
    end

Data flow

flowchart TB
    AnyThread["Any Thread<br/>(audio, render, IO)"]
    NetThread["Network Thread<br/>(xray-sock)"]
    MainThread["Main Thread<br/>(game loop)"]
    VaultConsole[("Vault Console")]
    VaultREPL[("Vault REPL")]

    AnyThread -->|"log_info() → MPSC queue"| NetThread
    NetThread -->|"TCP logs"| VaultConsole
    VaultREPL -->|"TCP repl_eval → SPSC queue"| NetThread
    NetThread -->|"SPSC queue"| MainThread
    MainThread -->|"executes Lua → mutates native state"| MainThread

Key design decisions

Logging

The logging system combines spdlog with dual sinks — file + TCP forward.

flowchart LR
    AppCode["App code"]
    Logger["spdlog logger"]
    FileSink["uwp_file_sink"]
    NetSink["uwp_net_sink"]
    LogFile["LocalState/xray.log"]
    MPSC["MPSC queue"]
    NetThread["Network thread"]
    Vault["Vault"]

    AppCode --> Logger
    Logger --> FileSink
    FileSink --> LogFile
    Logger --> NetSink
    NetSink -.->|"when connected"| MPSC
    MPSC --> NetThread
    NetThread -->|"send() TCP"| Vault

Log levels

DEBUG, INFO, WARN, ERROR, FATAL — each log entry includes a tag (e.g. AUDIO, RENDER, FS) and the thread ID that emitted it, making it easy to diagnose threading issues.

Backpressure

If the Vault consumes slowly, the MPSC queue fills up. The policy is drop-oldest: the oldest log entry is discarded, and every 64 drops a synthetic warning is injected into the stream so the developer knows data was lost.

[WARN] [XB-INSPECTOR] 142 logs dropped due to backpressure

File log format

[08-07-2026 15:30:01.002] [INFO]  [GENERAL] Engine initialized
[08-07-2026 15:30:01.015] [DEBUG] [AUDIO]  XAudio2 mastering voice created
[08-07-2026 15:30:02.100] [WARN]  [RENDER] Texture ui_bg.png not found, using default
[08-07-2026 15:30:05.001] [ERROR] [FS]     Failed to open save slot 2: access denied

Remote REPL (Lua)

This is the killer feature. The Inspector embeds Lua 5.4 in your app and gives you a live shell — running inside your process, on your game thread.

> print(player.name)
Marcos
> player.health = 999    -- modifies C++ variable in real time
> dump(scene)
{
  active_cameras = 2,
  draw_calls = 1420,
  objects = {
    [1] = { name = "Player", pos = { x = 12.5, y = 0, z = -45.1 } },
    [2] = { name = "Enemy",  pos = { x = 8.3, y = 0, z = -30.0 } }
  }
}
> engine_reset()
OK

What you can do from the REPL

How it works

1. Developer declares bindings in C++ using xb::Inspector::bind() and xb::Inspector::bind_type()
2. Lua runs on the main thread at the start of each frame — zero data races
3. Commands arrive from Vault via TCP, queued in an SPSC queue
4. Each command is executed via luaL_dostring wrapped in lua_pcall — errors don’t crash the app
5. Results are sent back as JSON via the same TCP connection
6. A 100ms timeout prevents infinite loops from freezing the game

Safety

Exposing C++ to Lua

// Register a type with its fields
xb::Inspector::bind_type<Player>("Player",
    "health", &Player::health,
    "name", &Player::name
);

// Expose a specific instance
Player player1;
xb::Inspector::bind("player", &player1);

// Expose a function
xb::Inspector::bind_function("engine_reset", []() {
    Engine::reset();
});

In the Vault terminal:

> player.health = 50   -- modifies the real C++ Player object
> engine_reset()       -- calls the engine reset function

Network Protocol

The protocol is JSON over raw TCP, newline-delimited. Every message is a single JSON line.

Handshake (Xbox → Vault)

Sent immediately on connection:

{
  "event": "handshake",
  "protocol_version": 1,
  "payload": {
    "app_name": "OpenBurningSuite",
    "app_id": "com.trespordez.openburningsuite",
    "capabilities": ["log", "repl"]
  }
}

Log entry (Xbox → Vault)

{
  "event": "log",
  "payload": {
    "level": "WARN",
    "timestamp": "16:42:11.002",
    "tag": "AUDIO",
    "message": "Buffer underrun. Dropping frame.",
    "thread_id": 4712
  }
}

REPL command (Vault → Xbox)

{
  "event": "repl_eval",
  "payload": {
    "id": 1,
    "script": "player.health = 100; return player.name"
  }
}

REPL response (Xbox → Vault)

{
  "event": "repl_result",
  "payload": {
    "id": 1,
    "success": true,
    "output": "Marcos",
    "error": ""
  }
}

Connection lifecycle

sequenceDiagram
    participant Vault as Vault
    participant Xbox as Xbox

    Vault->>Xbox: TCP Connect (port 9000-9009)
    Xbox-->>Vault: Handshake (app_name, protocol_version, capabilities)
    Note over Vault,Xbox: Bidirectional continuous flow
    Xbox-->>Vault: Log stream
    Vault->>Xbox: repl_eval
    Xbox-->>Vault: repl_result
    Note over Vault,Xbox: ...
    Xbox-->>Vault: TCP Disconnect (app closed or crashed)
    Note left of Vault: UI: "Waiting for app..."

Port scan

The Vault scans ports 9000-9009 on the Xbox IP. Each open port that sends a valid handshake becomes a selectable agent. Full scan completes in <50ms on LAN.

For Developers

C++ (primary)

#include <xray/inspector.hpp>

int main() {
    xb::Inspector::start();

    // Bind variables for REPL inspection
    xb::Inspector::bind_type<Player>("Player",
        "health", &Player::health,
        "name", &Player::name
    );
    xb::Inspector::bind("player", &g_player);

    // Logging with tags
    xb::Inspector::log_info("Engine initialized");
    xb::Inspector::log_warn("AUDIO", "Buffer underrun");
    xb::Inspector::log_error("RENDER", "Shader compile failed");

    while (running) {
        // REPL commands are consumed and executed here
        update();
        draw();
    }

    xb::Inspector::stop();
}

C# (MoonSharp)

XbInspector.Start();

// Binding via reflection — MoonSharp discovers fields automatically
XbInspector.Bind("player", g_player);

XbInspector.LogInfo("Engine initialized");

while (running) {
    update();
    draw();
}

XbInspector.Stop();

Rust (mlua)

xb_inspector::start();
xb_inspector::bind("player", &g_player);
xb_inspector::log_info("Engine initialized");

CMake integration

add_subdirectory(path/to/uwp-xray-depot)
target_link_libraries(my_app PRIVATE xb-inspector)

Security

The Inspector is a development-only tool. It is never compiled into release builds.

#ifdef XB_INSPECTOR_ENABLED
    #define XRAY_LOG(level, tag, ...) xb::Inspector::log(level, tag, __VA_ARGS__)
    #define XRAY_BIND(name, ptr)      xb::Inspector::bind(name, ptr)
#else
    #define XRAY_LOG(level, tag, ...)   // no-op
    #define XRAY_BIND(name, ptr)        // no-op
#endif

A CI step verifies no XB_INSPECTOR_ENABLED symbols exist in release builds.

Non-Goals (v1)

• File transfer (handled by File Explorer / SFTP)
• App lifecycle management (deploy, start, stop — WDP territory)
• CPU/GPU profiling (future possibility)
• TLS/authentication (trusted LAN only, Dev Mode only)
• Binary protocol support (text-only)
• Multi-language REPL (Lua only for v1)

Roadmap

Reference

• Xbox library: uwp-xray-depot — xb-inspector C++ implementation with full docs
• Desktop app: XBVault/ViewModels/InspectorViewModel.cs
• Desktop UI: XBVault/Views/InspectorView.axaml
• Icons: XBVault/Assets/Views/InspectorView/*.png