Zork is here because a real game is a real compiler test — routing, database, AI narration, caching, and error handling all at once. Not nostalgia. Proof.
Every command you type is processed live by the Mohio compiler — a language still being built. Glitches are not only expected, they're the point. When you find one, scroll down and tell us what happened. You're not just playing a game. You're helping build a language.
Play Zork in Mohio
Zork is a text adventure from 1977. You navigate by typing plain English commands — no menus, no buttons. The Mohio version understands most standard text adventure commands and tries to handle anything unexpected gracefully. If it doesn't, that's exactly the kind of thing we want to hear about.
Text adventures work by typing plain English commands — a verb and usually a noun. Type what you'd naturally say: GO NORTH, TAKE LAMP, LOOK AROUND. The game responds to what you type. There are no menus, no buttons — just you and the parser.
Stuck? Type LOOK to re-read the room description. Most puzzles can be solved by examining everything and reading anything with text on it. If the game gives you a strange response or an error — that's actually useful to us. Scroll down and report it.
This demo exists to stress-test the Mohio compiler against a real application. Every bug report — wrong output, error message, command that did nothing, room that felt broken — helps harden the language. You don't need to be a developer to report. Just describe what happened.
When AI makes real decisions — money, health, eligibility, safety — you need compliance, agents you can govern, persistent memory, audit trails, and cost control you can prove. Finance, healthcare, government, logistics, and more.