AnyScene builds a dressed Blender scene from a one-paragraph brief

Write one paragraph like "Lisbon tram depot at dawn, one tram half-stripped for repair". AnyScene returns a Blender scene. Every prop is its own object. The lights are placed. The camera moves are scripted. The repository went up on 30 October by apekshik, and it is MIT. On 2 November it had 192 stars and 21 forks.

What the agent does

Claude Code is the agent. It follows a file in the repository called SKILL.md. That file is the whole process, step by step. No prop is modelled by hand. Each prop is generated as an image first. The image is then turned into a 3D model, twice, by two services on fal. The two are Tripo H3.1 and Meshy 7.1. The agent picks the better one by rendering both under the same light.

The agent then writes a script that places the big furniture, then the small clutter. It adds grime, haze, steam and rain. It places practical lights. It writes camera moves and renders them in Cycles.

Each step ends with a gate. The gate is a contact sheet the agent has to look at before moving on. A person checks the gates on the way through.

Five scenes to look at

The repository has five finished scenes. A Tokyo electronics repair shop at 1 AM has 86 generated props. A Tokyo ramen shop at last orders has 74. A Hong Kong dai pai dong has 78. A 1970s mission control is also there. A Paris bakery was built end to end on a fal GPU worker, from one reference image. No person was in the loop for that one.

The finished .blend files are not in the repository. They add up to tens of gigabytes. Each scene folder keeps the prop list, the model picks with reasons, the shot plan and the build scripts. The whole thing can be rebuilt from the agent's own notes.

What it costs and what you need

The author gives real numbers. Each prop costs about $1.65 on fal. That is one image and two 3D models. A 90-prop scene is therefore about $150 of fal spend. A build takes most of a day of agent time. On your own machine it adds one to two GPU-hours of final renders.

You need Blender 5.0, Node 20, Claude Code, a fal API key, ffmpeg with an H.264 encoder, and uv. You also need a GPU with 12 to 16 GB of memory for Cycles. The hosted endpoint on fal runs the whole build if you would rather not install any of that.

A short companion file called CRAFT.md sits inside the project. It is the review loop that makes the method work. Render it. Look at it. Name the problem precisely. Fix it in code. Check the fix from a view that shows it. Then get an outside critic.

Source

AnyScene on GitHub, by apekshik.