Opus 5.5 turns a GitHub issue into a self-updating 3D model
Opus 5.5 built geometry, a rig, a browser viewer and a pipeline from a single issue, so each change request comes back to the repo as a pull request with a fresh render.
HOLY SH*T. ONE GITHUB ISSUE TURNED INTO A LIVING 3D MODEL THAT REBUILDS ITSELF EVERY TIME SOMEONE ASKS FOR A CHANGE Claude Opus 5.5 built the whole thing from that first request: geometry, rig, viewer and the pipeline behind it one rule: the model lives in the repo and answers in pull requests here's how it works: → REQUEST: one issue describes the object in plain words. that's it → BUILD: mesh, rig and materials get generated and committed as editable source files → VIEW: a browser viewer lands in the repo so anyone can spin the model instantly → LISTEN: every new issue is read as a change request against the current model → PATCH: only what changed gets rebuilt, then a PR opens with a fresh render a 3D asset is normally a dead file. someone exports it once, and every change after that means opening Blender again here it stays alive. ask for a longer handle or a softer material, and it replies with a PR every PR comes with a new render, so you review the change by eye before you merge the source is code, not a binary blob. every version is diffable. you see exactly which part moved and why don't like the change? close the PR. the model stays exactly as it was. cost: zero teams have run software like this for years. running a 3D model like a codebase is the part nobody had wired up the 3D artist on this team is now a GitHub issue the first request, the repo layout and one full issue-to-render cycle are in the article below ↓
This post quotes another post: x.com/noisyb0y1/status/2105964235087856080