AI IDE List
AI IDE List

GPT-6 Astra
+ Blender

From Python scripts
to editable 3D scenes.

Explore what people are building when Astra writes Python, runs Blender, inspects the render, and revises the scene.

Explore 12 cases Try the workflow

Collection updated

Rendered U-shaped Solace house with furnished rooms, a courtyard, and a pool surrounded by woodland
Thomas Ricouard / OpenAI

Blender is the tool. Astra writes the instructions. The result can include geometry, materials, cameras, and source code you can edit.

See how it works

The case collection

See the result, the method, and what the evidence supports.

12 cases in this collection

Official case study

An editable furnished house, a Cycles camera tour, and an interactive Unreal Engine 5 walkthrough.

Thomas Ricouard / OpenAI

Architecture
Public project files

Three prompt-driven revisions, with the Python scripts, Blender scenes, renders, and session transcript on GitHub.

Simon Willison

Props & characters
Creator demo

A vintage drawing becomes a mechanical assembly. The creator reports 3,295 editable objects.

Tom Krcha

Mechanical
Official case study

A procedural collector with 5,120 panels in the Earthward composition, refined through preview renders.

Thomas Ricouard / OpenAI

Environments
Official case study

A hard-surface cruiser with a segmented ring, four detailed engines, and independently editable materials.

Thomas Ricouard / OpenAI

Mechanical
Public project files

A three-view concept drawing becomes a 28-part rover, then receives measured edits to its saved Blender scene.

Kingy AI

Mechanical
Official case study

A lily pond, bridge, and planted garden developed from references and successive material reviews.

Thomas Ricouard / OpenAI

Environments
Creator walkthrough

A 14-minute first GIF looked plastic. A reference image and five revision rounds produced a better Cycles result.

Leon Liu / liustack

Props & characters
Creator walkthrough

A reference-led workflow separates asset creation in Blender from scene assembly in Three.js or Unreal Engine.

Matt Shumer

Environments
Creator demo

A creator demonstration using property listing photos to reconstruct a house and produce a promotional walkthrough.

Yunfan Ye

Architecture
Creator demo

A Three.js game is recreated as Blender scenes for a trailer, with GPT Image 2 supplying image assets.

Meng To

Animation
Failure case

A computer-use attempt at a realistic bat illustrates the gap between operating Blender and producing convincing anatomy.

aollivier82

Limitations

“Public project files” means the author links editable downloads or a repository. Other outputs and timings are reported by their creators; this collection is not an independent benchmark.

Build. Render. Inspect. Revise.

The useful loop is the work between the first prompt and the final image.

Read the official workflow
  1. 1

    Define the reference

    Provide views, dimensions, and the parts that must remain editable.

  2. 2

    Build with Python

    Astra writes bpy scripts. Blender creates and saves the scene.

  3. 3

    Inspect a preview

    Render cheaply. Compare the silhouette, intersections, materials, and framing.

  4. 4

    Revise and export

    Fix visible problems, render again, then deliver the scene and required exports.

Blender CLI + Python

Start here for repeatable builds, scenes, and batch rendering. The agent runs Blender in the background with a saved script.

/Applications/Blender.app/Contents/MacOS/Blender --background --python scene.py
Local setup walkthrough

Computer use + Python

Use the interface to inspect a viewport or handle a UI-specific step. Scripts still do much of the scene construction.

See the house example

A running Blender session + MCP

Inspect and modify an open scene through Blender Lab's add-on and MCP server. Requires Blender 5.1 or newer.

The integration executes model-written Python. Blender recommends an isolated environment without sensitive files.

Blender's setup and guidance
First EEVEE donut on the left and the revised Cycles donut on the right
First EEVEE render → five rounds of revision in Cycles. Leon Liu / liustack

A saved render is only the beginning.

The donut's first version took 14 minutes and looked plastic. Better references, materials, and repeated visual checks improved the result.

The train's object count does not prove clean topology. The bat demo shows that a working Blender session can still produce unconvincing anatomy.

Start with an
editable scene.

Attach a clear reference for a mechanical object, prop, or house. Ask for saved source files and visual checks as part of the deliverable.

This starter prompt adapts the practices in the examples. It is not an original prompt from a featured case.

.blend.py.glbPreviewsTurntable
Read Simon's reusable Blender skill
Blender scene starter
Use the locally installed Blender through its Python API.
Build the attached reference as an editable Blender scene.

Requirements:
- Keep major components separate and clearly named.
- Match proportions and silhouette before adding detail.
- Keep materials independently editable.
- Preserve the source Python scripts and an editable .blend.
- Export a GLB and a turntable video.
- Render front, side, three-quarter, and close-up views.

Workflow:
1. Analyze the reference and identify uncertain details.
2. Build the primary geometry and check proportions.
3. Render a low-cost preview.
4. Compare the preview with the reference.
5. Fix geometry, intersections, and floating parts.
6. Add secondary details, materials, lighting, and cameras.
7. Render and inspect again. Revise what still looks wrong.
8. Save the final scene, scripts, exports, and previews.

Do not consider the task finished merely because Blender ran
without errors. Visually inspect the render before completion.