Vídeo IA / 3d Scene

Living 3D model generated from GitHub issues

Criador@0xWast3 ↗

Referência criativa

Criador: @0xWast3 ↗

01 / Crie sua versão

Crie sua versão

01
Veja o resultado e observe o ritmo
02
Leia as notas originais do criador
03
Use a referência para desenvolver sua ideia

02 / Fonte e créditos

Fonte e créditos

Criador@0xWast3

Publicação original ↗

Notas do criadorGrátis

Modelo: Opus 5.5 ↗
Categoria: 3d Scene ↗

Notas do criador

Anthropic turned one GitHub request into a living 3D model that answers every new issue with a rebuilt version of itself Opus 5.5 builds the whole system from that first request, from geometry and rig to the viewer and the pipeline behind it. > REQUEST - one issue describes the object in plain words, nothing else needed > BUILD - mesh, rig and materials generated and committed as editable source files > VIEW - a browser viewer added to 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 pull request opens with a fresh render A 3D asset is normally a dead file. Someone exports it once, and every later change means opening the software again. Here the model stays alive inside the repo. Ask for a longer handle or a softer material, and it answers in a pull request. Each pull request carries a new render, so the change gets reviewed by eye before anyone merges it. Because the source is code and not a binary blob, every version is diffable. You see exactly which part moved and why. Rejected changes cost nothing. Close the pull request and the model stays exactly as it was. Teams already run software this way. Running a 3D model like a codebase is the part nobody had wired up. The first request, the repo layout and one full issue-to-render cycle are pinned in the article.

Publicação original ↗