The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.
Phaser, as a Harness agent
Harness agent package for Phaser: describe a game in the terminal pane — a breakout, a platformer, a shooter, a puzzle — and play it in the pane beside it while the agent writes it in Phaser 4. Runs on Codex.
harness.json— engine, template, skills, toolchain, and this package's own viewer.viewer.sh→viewer.mjs— Vite's dev server on the workspace (its ownvite.config.mjs), on the port Harness hands it, loopback only, inside a game frame (viewer/). Vite's HMR is what makes the pane live: the agent saves a scene, the game reloads — and goes back to the scene the player was in. The frame adds screen sizes (fit, game size, phone, tablet, 1×), pause, restart, a debug toggle that draws the physics bodies with an fps/scene/bodies HUD, full screen, the focus and controls hint, and build and runtime errors as a card with the file, the line and the code — never a blank pane. Two small scripts are injected into the page Vite serves (never into a build): a guard for errors and a probe that finds thePhaser.Game.toolchain/setup.sh— onenode_modulesin this directory (Phaser 4.2.1, Vite 6, terser, pinned inpackage.jsonandVERSIONS) that every workspace symlinks to, so a new game is instant and there is one copy of Phaser on the machine.toolchain/verdict.py— the phases the pane header shows: Write (an entry and a scene), Build (vite build— the compile check; parse and resolve errors become findings with a file and a line), Play (a scene withcreate()and input handling).python3 -m unittest discover -s toolchaintests the judge without Vite.skills/— Phaser Studio's own 28 agent skills, vendored verbatim (PROVENANCE.md), plusharness-phaser: the workspace, the pane, the keyboard-focus rule, the verdict.template/— a Vite + Phaser 4 project, 960×540 scaled to FIT, whose starter is a playable breakout drawn entirely withGraphics→generateTexture; no image files anywhere.
The one thing worth knowing
The pane is a webview, and a webview has no keyboard focus until the player clicks inside it. So
every game here opens on a gate — a title, "Click to play", this.input.once('pointerdown', …) —
and ships on-screen touch controls beside the keys, because pointer input needs no focus. That rule
is in AGENTS.md, in skills/harness-phaser/SKILL.md, in the template, and the verdict says so
when a workspace loses it.
Credit and stewardship
Phaser is Richard Davey's and Phaser Studio's — phaserjs/phaser,
phaser.io — under the MIT License (LICENSE-phaser). Nothing of it is
changed here: the engine is installed from npm as released, and Phaser Studio's agent skills are
copied into skills/ verbatim, at the commit recorded in PROVENANCE.md, as the MIT licence
allows. This folder is the Harness wrapper — the manifest, the pane script, the template, the
toolchain, the verdict, the one harness-phaser skill — written by Autonomous to bring Phaser into
Harness, on the project's behalf, to bootstrap the catalogue. The wrapper is MIT too (LICENSE).
If you maintain Phaser and want to own its Harness package, it is yours: open an issue on
OpenHarness and we move this folder into a
repository of yours and point the registry entry at it. Until then: bugs in Phaser belong upstream, bugs in
the wrapper belong here, and a newer Phaser is a bump of package.json, template/package.json and
VERSIONS plus a refresh of skills/ (PROVENANCE.md has the commands).
| Homepage | https://phaser.io |
| Upstream | https://github.com/phaserjs/phaser |
| Licence | MIT |
harness dsh check . # conformance
harness dsh install "$PWD" --link # this checkout as the installed agent
python3 -m unittest discover -s toolchain # the verdict's judge and the scripts, without vite
node --test 'test/*.test.mjs' # the pane's server on a real Vite (after setup)