Blender Agent Studio v0.6.4

Project

Contributing

Report bugs, run the checks, and keep generated output out of commits.

Report a bug

Open an issue with your host (Codex or Claude Code), plugin and Blender versions, what you asked for, and what happened. A render or an error log helps. Leave out credentials, private assets, and sensitive agent traces.

Share what you made

Share an example with the prompt, agent and model, Blender version, and a render. Include the Python build script when you can. If you want the example featured in the docs, say so and share only files you have permission to publish.

Testing another harness? Follow the compatibility report guide.

Run the checks

From the repository root:

bun install --cwd plugins/blender-agent-studio
bun run check
bun run test
bun run test:python

Set BLENDER_EXECUTABLE or put Blender on PATH to include the live Blender tests. For the Rust tests, build the runtime first:

bun --cwd plugins/blender-agent-studio run setup:runtime
bun --cwd plugins/blender-agent-studio run test:runtime

After editing references/astra-workflow.md, run bun tools/sync-guidance.ts to update the copy bundled with each skill.

Keep both hosts supported

The plugin has separate Codex and Claude Code marketplace and plugin manifests. Keep their names, versions, descriptions, and MCP entry points aligned; bun run check verifies them. With the Claude Code CLI installed, also run:

claude plugin validate .
claude plugin validate plugins/blender-agent-studio

To try a local checkout in Claude Code, run claude --plugin-dir plugins/blender-agent-studio from the repository root.

Work on these docs

The site lives in site/. Pages are Markdown files in site/content, and a small Bun and TypeScript builder in site/src turns them into static HTML.

bun install --cwd site
bun run docs:assets  # restores the checksum-pinned benchmark gallery
bun run docs:dev     # http://localhost:4321, reloads on save
bun run docs:test    # checks generated pages, search, and interactions
bun run docs:build   # writes site/dist

The build fails if a skill or MCP tool is missing from these pages, or if a link points to a page or heading that doesn't exist. Pushes to main deploy the site to GitHub Pages.

Ground rules

  • Don't commit generated models, exports, renders, benchmark runs, or agent traces.
  • Keep Blender execution bounded. Don't add a generic arbitrary-Python MCP tool.
  • Treat one benchmark generation per condition as directional evidence, not a capability claim.

The development guide covers benchmarks and more setup detail.

MIT licensed. Not affiliated with the Blender Foundation.