Windows Play mode stabilized + LLM debug proxy for developers
Play mode on Windows is now stable thanks to an editor Socket stack fix; a new FORGEAX_DEBUG_PROXY env var lets developers capture and inspect all LLM API traffic in real time; desktop app packaging on Windows has been fixed; and the reel-game runtime architecture has been designed as an engine-level game runtime subclass.
Windows Play mode: finally stable
Play mode on Windows had been intermittently failing due to a Socket stack issue in the editor. The underlying WebSocket export was missing from the desktop build path, causing the engine preview iframe to lose its connection to the editor host. This has been fixed — Play mode on Windows now works as reliably as on macOS.
LLM debug proxy for developers
A new opt-in environment variable FORGEAX_DEBUG_PROXY has been added. When set, it spins up a local HTTP proxy that captures every outbound LLM API call (to Anthropic, OpenAI, Gemini, etc.) and logs the request/response pairs. This is invaluable for debugging agent behavior — you can see exactly what prompt was sent, what the model returned, and how long each call took. Set it in your .env and the proxy starts automatically with bun fx start.
Windows desktop app packaging fixed
The Tauri 2 desktop build for Windows was failing due to a missing dependency export in the interface package. This has been resolved — bun fx build app now produces a working .exe installer on Windows.
Reel-game runtime architecture
A design spec landed for the reel-game (interactive film) runtime, positioning it as a first-class game runtime subclass within the engine. This means interactive films will share the same ECS pipeline, scene graph, and asset system as regular games, rather than being a separate sidecar. The implementation will follow in upcoming releases.