Choose the interface your agent can reach
- Code execution with Node.js 22.13 or newer: use the downloadable CLI for local project files, command batches, Lua scripts, rendered previews, and exports. This is the most direct option when the agent has a terminal but no interactive canvas.
- Browser page execution: a running current editor exposes window.pixelwall version 1 for inspection, revision-checked command batches, Lua, previews, saves, exports, Undo, and Redo.
- Browser or desktop computer control: an agent with approved mouse, keyboard, screen, and file access can operate the visible editor. The desktop Help menu links back to this guide.
- Compatible browser tool registration: when a host supplies a modelContext registration surface, the editor registers its ordinary command tools there. Availability comes from the host environment.
- Read-only web or chat access: the agent can read these pages but cannot edit PixelWall unless its host also provides one of the interfaces above.
What is available today
The supported automation surfaces are the local CLI, window.pixelwall in the current editor, bounded Lua 5.4 scripts, JSON command batches, and deliberate computer control. They use the same document and rendering engine in the web and desktop editors.
PixelWall does not currently publish a standalone MCP server, public REST editing API, JavaScript or Python SDK, or universal agent protocol. There is no automatic connection from an arbitrary ChatGPT conversation. An agent needs explicit access to the local CLI, the running editor page, or the visible application.
Run the complete ninja-panda example
This example uses 63 ordinary PixelWall commands to create a 24 × 24 ninja panda with nunchucks and three idle-animation frames. The downloadable command file is readable JSON. The finished project and first rendered frame let an agent compare its result before revising the commands.
Download and extract the CLI, then keep the command file in the same working folder. The first command creates an empty project. The second applies the complete animation as one edit. The third renders frame zero at 8× for inspection. Change the JSON and apply it to a fresh project for another revision.
node pixelwall.mjs new --width 24 --height 24 --name "Ninja Panda Idle" --out ninja-panda.pixelwall
node pixelwall.mjs apply ninja-panda.pixelwall --commands agent-ninja-panda-commands.json --out ninja-panda-animated.pixelwall
node pixelwall.mjs inspect ninja-panda-animated.pixelwall
node pixelwall.mjs render ninja-panda-animated.pixelwall --frame 0 --scale 8 --out ninja-panda-preview.png
Safety, saving, and licensing
Inspect the current document and use expectedRevision before a browser edit when another person or tool may also change it. Treat a successful apply and a successful save as separate results. Keep a downloaded project backup before unattended batches or application replacement.
Scripts and commands cannot bypass format or Pro checks. Individual PNG, BMP, and TGA frames and editable projects are free. GIF, atlas, sheet, and game-package exports require a valid Pro license. Lua is bounded and has no arbitrary file, network, or process access; a deliberately selected CLI JavaScript module runs with ordinary Node.js access.
Common questions
Can any ChatGPT conversation directly run PixelWall?
No. The conversation's host must provide terminal access, browser page execution, or approved computer control and expose PixelWall through that environment.
Does PixelWall have an MCP server or public REST API?
Not currently. Use the documented CLI, browser command API, Lua scripting, JSON command batches, or computer control.
Can an agent create pixels without moving the mouse?
Yes. A code-execution agent can build and revise native projects through the CLI, render PNG previews for inspection, and export supported formats.