Open the game you are already making. A coding agent works inside it, Studio recipes turn prompts into sprites, tilesets, UI and VFX your engine can load, and every build gets verified.
Kaia needs an 8-direction walk in the player scene. Use her character card.
I'll run the walk-sheet recipe with Kaia's card, slice the pick into frames and wire up an AnimatedSprite2D.
Done: 8 directions × 6 frames at 10 fps. Check, build and run passed.
An 8-direction walk cycle on a strict grid, keyed to transparency and sliced into per-frame PNGs.
Key art, turnarounds, walk sheets, icon sets and effects — from pixel art to stylized 3D, ready to drop into the project.
Examples generated with OpenPixo recipe prompts and post-processed with pixo asset. Results vary by model.
OpenPixo opens your Godot, Unity, Phaser or Three.js project in place and recognises the engine, its build commands and where assets belong. Nothing is copied or moved.
Codex works in the project with streaming output, approvals, interrupt and resume. Claude Code and OpenCode join in v0.2.
Make the player face the way they walk, in all eight directions.
I mapped the input angle to the eight rows of the walk sheet:
extends CharacterBody2Dconst DIRS := ["down", "down_left", "left", "up_left", "up", "up_right", "right", "down_right"]@onready var sprite: AnimatedSprite2D = $Spritefunc _physics_process(_delta: float) -> void:var input := Input.get_vector("left", "right", "up", "down")velocity = input * SPEEDif input != Vector2.ZERO:var index := wrapi(roundi((input.angle() - PI / 2) / (PI / 4)), 0, 8)sprite.play("walk_" + DIRS[index])else:sprite.stop()move_and_slide()
Pick a recipe, fill in a character card or a few fields, and get candidates already keyed, sliced and checked. Adopt the ones you like; they land in your project as ordinary files.
OpenPixo runs your engine's headless check and build and can capture a screenshot, so the agent can change, run, look and fix in one loop.
Illustrative timings. Headless verification arrives with the v0.2 game harness.
Each recipe pairs a tuned prompt with the processing games need: keying to transparency, slicing sheets, checking grids and seams. Here they are, running the way a game uses them.
From a character card to a 6 × 8 sheet, keyed and sliced into 48 frames. Shown here straight from the sheet.
openpixo/sprite-walk-8dirImpacts and spells on black for additive blending, 16 frames from spark to fade.
openpixo/vfx-sequence
Same character, same scale, every view on one baseline — ready to become a character card.
openpixo/character-turnaroundFar, mid and near layers that tile horizontally, with everything above the scenery transparent.
openpixo/parallax-layers
One sheet, one style, sliced into single icons at your size.
openpixo/item-icon-setCorners stay put while edges and centre stretch. Live CSS border-image above.
openpixo/ui-nine-sliceWraps on all four edges, resized to tile size and seam-checked.
openpixo/tileset-seamless360° equirectangular panoramas at 2048 × 1024 for a sky sphere — panning here.
openpixo/skyboxAlso in Studio:BGM loopsUI soundsNPC voice lines3D model from imageGame startersGame featuresAll recipes →
Deterministic operations keep your originals and write new files next to them. Agents call the same commands mid-task, with --json output.
BeforeAfterpixo asset remove-bg kaia_turn.png --mode chroma --color FF00FFKey out the recipe background to real alpha.
BeforeAfterpixo asset pixelate cottage.png --size 144Down to a pixel grid, with optional palettes and dithering.16 colours extracted from the harbour scene:
Engines
Agents
Official recipes, skills, MCP presets and project templates, each with a stated license. The free catalog comes first; official paid packs bought with credits are planned for v0.4.
OpenPixo opens the folder you picked and writes results there as ordinary files. Originals are kept; nothing is uploaded to OpenPixo.
Prompts go straight from your computer to the agent or provider you configured. You approve permission requests as they come.
Local use needs no OpenPixo account. A later optional account only covers credits, hosted generation and paid store items.
Something missing? Ask on GitHub.
A local-first agent workbench for independent game developers. It puts your project files, image and audio previews, agent conversations, Studio recipes and project extensions in one desktop workspace, so you can keep moving a game you are already making.
They were generated with an image model from the prompts in OpenPixo's built-in recipes, then keyed, trimmed, resized and sliced with the same code that runs pixo asset. The key art was generated with the same model from written briefs. We picked the best candidates; your results depend on the model and provider you use.
Local use needs no OpenPixo account. You use your own agent account or a supported provider; subscriptions, API costs and limits are set by the provider you choose. A later version adds an optional account for credits, hosted generation and paid store items; everything local keeps working without signing in.
Your game stays in the folder you picked. When you run a task, the prompt and the project content involved go to the agent or model service you configured — a local workbench is not an offline model. See Privacy.
The Windows x64 preview is in local testing: install, launch, restart and uninstall checks pass, and the installer is not signed yet. The first public release is planned as a signed 0.2.0-beta.1 with SHA256 checksums on the download page. No other platform is promised yet.
In a local OpenPixo checkout, with Node 24.x, pnpm 10.33.2 and native Codex 0.160.0 or later:
pnpm install --frozen-lockfile
pnpm tools-devThe lifecycle tool starts the daemon, web app and desktop shell together. Public source is not published yet.
The first public release is planned as 0.2.0-beta.1, with a signed Windows installer and SHA256 checksums on the download page.