3D for agents.

A spectral path tracer your coding agent drives from the terminal.

claude code · opus 4.8 · driving glyphaerecorded session
glyphae --view 127.0.0.1:7878
params.tire_lugs

72 real frames, path-traced at 500 spp. Change any other knob and the engine renders it — on your machine, not this page.

Driven by the agent you already run

  • Claude Code
  • Codex
  • Kimi CLI
  • opencode
  • Aider
  • Gemini CLI
  • Cline
  • Your own harness

No plugin and no integration: glyphae --help-ai prints the manual, and anything that can run a binary can drive it. Names are ours to state, not theirs to endorse.

Construction

Nothing here was modelled by hand.

The tire is an op graph: four operations the engine replays from a text file. Change one number and the whole build runs again, so nothing is ever destroyed.

Tire construction, step 1: revolveglyphae --tire-build · op 01 revolve
The finished tire, path-traced at 3000 samples
The same scene, converged: 3000 samples, denoised, 2200 × 1400. glyphae --render-scene work.scene tire.png 3000 2200 1400

Motion

It moves, frame by frame.

Turntables, seamless loops, camera arcs, build reels and real physics — eight sequence modes that write numbered frames. Both clips below are engine output, played back at 24 frames a second.

Seamless loopThe same tire, one full turn — last frame meeting the first by construction, not by trimming. Physics, turntables, camera arcs and build reels are the other sequence modes.glyphae --tire-loop frames/ 48 420 1000 750

Where it stops: glyphae writes the frames. Encoding, sound design, music and the edit happen in your own tools — there is no audio or timeline in the binary, and the page will not pretend otherwise.

v0.3.0shipping today
16.0 MBone binary per platform
macOS · Linux · WindowsMetal, Vulkan and DX12
Freeno account, no key

Why

Your agent is the 3D artist. This is its tool.

Frontier coding agents already reason about geometry, materials and light — and then hit a wall, because every 3D tool assumes a human with a mouse. Glyphae is the hands: a binary Claude Code, Codex or Kimi CLI can run, whose scene is a file, whose change is a diff, and whose frame is a pure function of both.

How

Scenes are programs, and one window never closes.

Geometry is an op graph evaluated deterministically; materials, camera and lighting are plain-text knobs. Same input, same pixels, every time. A live viewport watches the file and reloads on save, and answers a JSON socket — so you and the agent are looking at one frame instead of trading screenshots.

What

A spectral path tracer, in one binary.

One compute invocation is one pixel is one spectral path: wavelength sampled per path, Sellmeier dispersion, real caustics. A draft tier validates motion and framing in seconds; the final tier is the physical one. Rust and wgpu, so it picks Metal, Vulkan or DX12 on its own, with nothing to install.

Glyphae rendered our own production work for months — films, packshots and stills that shipped to clients — before we handed the binary to anyone else. The binary you download is the one that made them. Download counts and community work appear here when there are real ones to show.

Put it on your machine.

One binary, no dependencies, free. Point your agent at glyphae --help-ai and it can drive the whole thing.