The companion gets state, not guesses.
Browser emulation can expose semantic runtime memory. loot.moe relays that state so the game can run on one device while your AI companion lives on another.
loot.moe turns runtime game memory into structured, addressable state an AI companion can understand. Not pixels. Not copied stats. The live game underneath.
Browser emulation can expose semantic runtime memory. loot.moe relays that state so the game can run on one device while your AI companion lives on another.
The current semantic-runtime proof already decodes a meaningful slice of player state directly from emulated Nintendo DS main RAM.
A game session can publish state to loot.moe. A companion surface can retrieve the same session without sharing a screen.
Each game gets an adapter. The companion-facing layer stays stable: live state, latest loot, build, equipment and events.
This stand-in does not include or host ROM files or copyrighted game assets. The product layer is the runtime state bridge.
For the first real version, loot.moe does not need to call an LLM itself. Its job can be simpler and cleaner: publish the live semantic state securely, then let ChatGPT or another agent read it through a connector.
This stand-in ships with read endpoints for the current state, latest loot and build, plus a state-ingest endpoint for the browser runtime. The OpenAPI document is generated by the app at /openapi.json.
loading…