Experimental

Blender.
Through its own interface.

Reach into the scene through an application-native driver.

  • Scene, object, material and collection operations
  • Bounded RNA, operator and add-on metadata discovery
  • PNG rendering and scoped .blend open/save

Where the boundary is.

Check the driver documentation for the exact version and operation surface. A passing gate is not a claim of complete Blender or add-on compatibility.

What the evidence says.

The frozen main revision has a passing Blender 4.5.14 LTS integration gate: real sandboxed driver execution, introspection, object/material mutation, a CPU render, .blend save and a CLI-to-broker smoke path.

This is an editorial summary of a frozen source revision, not a probe of your installation. A successful job does not automatically certify other versions, environments or operations.

Start with the contract.

Read the integration’s own README and security notes before enabling it. Owner-assigned identity, required grants and application dependencies must be configured explicitly. Registration alone does not authorize execution.

Open the Blender source documentation ↗

For the common model, read drivers and providers and permissions and consent.