The editor, in your browser

The same editor the desktop build ships — its scripts, its five personas, its inspector — compiled to WebAssembly and drawing through WebGPU. The project it opens is unpacked into a filesystem that lives in the tab, so you can move a node, edit a script and watch it reload, without installing anything.

hello 3D — a spinning cube, a ball, physics, a HUD labelangrynerds 2D — a slingshot game, 38 nodes, widgetsrig 2D skeleton — bones, a skinned leg, two-bone IK

Click the canvas to give it the keyboard. Your edits live in this tab only — nothing is uploaded, and closing the page discards them.

What works, and what does not

The tree, the viewport and its gizmos, the inspector, the docks, the personas and the script editor all work, because they are the same Rune scripts the desktop editor runs. A save writes into the tab's filesystem and the editor reloads from it, so hot reload works without a file watcher.

Not yet: sound, which is stubbed on WebAssembly; a project that outlives the tab, which wants somewhere to keep it; loading a project of your own; and exporting a native build, which needs a linker the browser has not got. The roadmap tracks those. To edit a real project today, build the editor — and /play is the engine alone, running a game without the editor around it.