O88-bit
▶ PLAY BROSIDE-SCROLLING PLATFORMERSmall screen. Big personality.
Sprites, chiptunes, and a tiny Lua playground. Start here and make every pixel count.
- screen
- 128×128
- colours
- 16 fixed
- cartridge
- 32KB
01
THE LADDER
Three machines. Three ways to make.
Omibit is a family of finished fantasy consoles. Pick the constraints that spark an idea. Each has its own character; all share the same cartridge format.
▶ PLAY BROSIDE-SCROLLING PLATFORMERO16SNES-class
▶ PLAY GPXMODE 7 RACINGA little more room to explore.
Richer sprites, 32 colours, and Mode 7 landscapes. Build a bigger adventure—or one more lap.
- screen
- 256×224
- colours
- 32 fixed
- cartridge
- 256KB
O32PS1-class
▶ PLAY MEADOWLOW-POLY EXPLORATIONStep into another dimension.
Textured triangles, low-poly worlds, and that unmistakable 3D wobble. Make somewhere to get lost.
- screen
- 320×240
- colours
- 256 fixed
- cartridge
- 1MB
All three machines are implemented. The 1.0 compatibility contract is under review. Built to last.O64 RESERVED / NOT A MACHINE
02
THE CART
That picture is the whole game.
Code, sprites, maps, and sound—all inside a real PNG. Keep it in a folder. Send it to a friend. Open it in the console and play.
- 01MAKE
Write some Lua. Draw a sprite. Give it a sound.
- 02EXPORT
Save your game as one image. The cartridge is yours.
- 03PASS IT ON
Share the original PNG. Your friend can play or remix it.
How does a picture store a game?
Game data lives in the low two bits of each RGBA channel—one byte per pixel. The visible label stays an image; the console reads the code and assets inside. Keep the original PNG intact: resizing or recompressing it can damage the game data.
Read the cartridge guide ↗
↓ SAVE THIS GAMEA real game, not a mockup.
Load this PNG in the console to play.
03
AGENTS
An idea. A few iterations. A playable cart.
Make it yourself, or click build with an agent in the editor: copy the address it gives you into any MCP client, and the agent writes code, runs carts, inspects screenshots, and tries again — right on this site, no install. Here’s how an actual game came together.
ACTUAL OUTPUT / O8STEP 1
the ring
static scene first: title, ring guide, ship marker. something to verify against.
- ›
load_cartOK - ›
runOK - ›
screenshotOK - ›
state_hashOK
RECORDED STATE HASH
6ce4e0bdSELECT A STEP TO SEE IT EVOLVE
Recorded output and tool calls from the original session. Watch the full build ↗
One-click on the site, or the local CLI and stdio MCP when you prefer offline, repo-based workflows. One core either way.
Connect your agent ↗04
DETERMINISM
Same game. Same inputs. Same result.
A ranked replay starts fresh and records your buttons. Run it again and the machine produces the same frames and state hash. That makes scores verifiable and agent creations testable.
cart bytes + input log → frames + state hash
STATE HASH
--------STATE HASH
--------Same cart. Same 120 inputs.
Two independent O8 instances running here in your browser. Every frame and state hash is compared—not a prerecorded animation.
What keeps the machines consistent?
The browser and headless tools use the same deterministic core. A golden corpus checks expected frames and hashes on both hosts. The state hash checks RAM and the frame counter; replay verification reruns the cart from its initial state.
Read the compatibility commitment ↗05
YOUR TURN
Pick a cart. Or start with a blank screen.
The console, editor, and games are all in your browser. No install. No account. Just open a machine and see what happens.