Blender workflow

Default approach

Treat Blender Python as the primary control interface.

For substantial work, prefer this order:

1. Write or update version-controlled Python using bpy, bmesh, mathutils, and Blender's data APIs.
2. Run that code with the actual Blender executable, normally in background mode.
3. Inspect both machine-readable scene state and rendered images.
4. Iterate until the structural and visual checks pass.
5. Use Blender MCP when a live Blender session is genuinely useful.
6. Use GUI/computer-control tools only for tasks that are awkward or impossible through Blender's programmatic interfaces.

Do not replace a good Python workflow with a long sequence of opaque GUI clicks or granular MCP mutations. Substantial edits should be represented in scripts where practical so they can be diffed, rerun, debugged, and reused. The .blend file is still a legitimate project artefact; not every existing scene needs to be regenerated from scratch.

Run scripts through Blender