Hypertool is a browser studio that turns a prompt into a live, controllable visual (WebGL, shaders, typography, motion) with a shareable URL, video export and real code. Each of these is something you get, and the engineering behind it.
A design canvas where everything is alive
The stage is a full design engine drawn on your GPU (WebGPU, with WebGL 2 as fallback). Vector shapes, text, images, video, 3D models and your running pieces share one infinite canvas with layers, undo and Figma's shortcuts, and every piece keeps running while you zoom out to see the whole system. Any layer exports as SVG, PNG, JPG, WebP or code.
Speaks Figma, both ways
Paste a selection from Figma and it lands on the stage as editable layers (vectors, text with its fonts, images), not a screenshot. Copy layers on the stage and paste them straight back into Figma. Text is set with professional shaping (HarfBuzz, FreeType, right-to-left and mixed scripts), so type looks the way it was designed.
An agent with eyes and hands
The agent works the stage the way you do. It takes screenshots up to 4K, reads the layer tree, samples a contact sheet that tells it whether the motion moves and settles, and reads the piece's console errors, frame rate and memory. It clicks, drags, types and moves controls to test what it built, lays out whole scenes on the stage in one undo step, and fixes what is off before it hands back.
Real builds, with no server to wait for
On a laptop or desktop, opening a project starts a complete development environment inside the page: a filesystem written in Rust and compiled to WebAssembly, a shell, real processes, a package manager, git and a live dev server. Your piece is installed, built and run on your own machine, so a change shows up the moment it is written, the agent's included.
The whole npm ecosystem, not a toy subset
Packages install for real, into a real node_modules: Three.js, p5.js, PixiJS, GSAP, Tone.js, React, Vite and anything else that runs in a browser or in plain Node, including libraries that ship WebAssembly. Common packages come from a pre-extracted cache, so their installs skip most of the downloading and unpacking.
Controls that turn a result into a tool
Every control lives in one plain file in the project, controls.toml, and runs on its own engine compiled to WebAssembly, in a worker of its own, off the piece's thread. The panel and its automation travel with every share link and every export: whoever gets the piece gets the tool.
Links that never change under people
A share link, its embed and an export are made from a single build bound to the exact version it came from, so they can never disagree. A link never changes under the people you sent it to; publishing again makes a new version, and a remix starts from exactly the version that was shared.
Video of exactly what ran
Record encodes the running piece on your machine to H.264 MP4 with its sound mixed in, frame by frame as it paints. Nothing goes to a render farm and nothing is re-rendered, so the video is exactly what ran.