Skip to content
Back to search

blender-agent-studio

Codex plugin for reproducible Blender modeling, validation, animation, MCP tooling, and agent benchmarking

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/ifBars/blender-agent-studio with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/ifBars/blender-agent-studio'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/ifbars--blender-agent-studio/badge.svg)](/listings/ifbars--blender-agent-studio)

HTML

<a href="/listings/ifbars--blender-agent-studio"><img src="/api/listings/ifbars--blender-agent-studio/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

You'll need [Codex](https://developers.openai.com/codex) or [Claude Code](https://code.claude.com) with plugin support, [Bun](https://bun.sh), and Blender. Blender 5.2 LTS is the tested version; use Bun 1.3.5 or newer. Both hosts install the same skills, MCP server, and SceneIR tools from this repository.

**Codex**

codex plugin marketplace add ifBars/blender-agent-studio
codex plugin add blender-agent-studio@blender-agent-studio

**Claude Code**

claude plugin marketplace add ifBars/blender-agent-studio
claude plugin install blender-agent-studio@blender-agent-studio

Inside a Claude Code session, `/plugin marketplace add ifBars/blender-agent-studio` and `/plugin install blender-agent-studio@blender-agent-studio` do the same.

Put `blender` on your `PATH`, or set `BLENDER_EXECUTABLE` to its location. For example, in PowerShell:

$env:BLENDER_EXECUTABLE = "C:\path\to\Blender\blender.exe"

Start a new Codex task or Claude Code session after installing or updating the plugin. In Codex, invoke a skill as `$blender-agent-studio:blender-modeling-workflow`; in Claude Code, as `/blender-agent-studio:blender-modeling-workflow`. Both hosts also pick the relevant skill from a plain request.

For the optional scene-understanding tools, build the Rust runtime in the installed plugin directory with `bun run setup:runtime`. See [scene understanding](docs/scene-understanding.md) for setup, examples and measurement limits. The existing tools do not require Rust.

<details> <summary>Update an existing GitHub installation</summary>

Codex:

codex plugin marketplace upgrade blender-agent-studio
codex plugin add blender-agent-studio@blender-agent-studio

Claude Code:

claude plugin marketplace update blender-agent-studio
claude plugin update blender-agent-studio@blender-agent-studio

</details>

Prefer skills only? See the [alternative installation options](docs/development.md#skills-only-installation) and [browse the workflows on skills.sh](https://skills.sh/ifbars/blender-agent-studio).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 15 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "blender-agent-studio",
  3. "description": "Marketplace for a free, open-source Blender AI plugin. Build with local Blender from the agent you already use.",
  4. "owner": {
  5. "name": "Bars"
  6. },
  7. "plugins": [
  8. {
  9. "name": "blender-agent-studio",
  10. "source": "./plugins/blender-agent-studio",
  11. "description": "Free, open-source Blender AI plugin for modeling, animation, rendering, validation, and repair with local Blender. Codex and Claude Code installers.",
  12. "category": "development"
  13. }
  14. ]
  15. }
README.md · README · 289 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. # Blender Agent Studio
  2. **Describe a model, scene or animation to Codex or Claude Code. Get back an
  3. editable `.blend`, the Python that built it, and renders your agent has checked.**
  4. A free, open-source Blender AI plugin. It runs your local Blender and needs no
  5. extra service, API key or subscription beyond the agent you already use.
  6. [![Validate](https://github.com/ifBars/blender-agent-studio/actions/workflows/validate.yml/badge.svg)](https://github.com/ifBars/blender-agent-studio/actions/workflows/validate.yml)
  7. [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
  8. [![Docs](https://img.shields.io/badge/docs-ifbars.github.io-E87D0D.svg)](https://ifbars.github.io/blender-agent-studio/)
  9. [Docs](https://ifbars.github.io/blender-agent-studio/) · [Quick start](#quick-start) · [Examples](https://ifbars.github.io/blender-agent-studio/comparisons/) · [How it works](#how-it-works) · [Workflows](plugins/blender-agent-studio/skills) · [Development](docs/development.md) · [Report a bug](https://github.com/ifBars/blender-agent-studio/issues)
  10. [![A furnished reading room built with Blender Agent Studio and Claude Sonnet 5.5](https://ifbars.github.io/blender-agent-studio/benchmarks/gallery-matrix/scene-character/decorated_reading_room--claude-sonnet-5-5--r01/plugin/preview/hero.png)](https://ifbars.github.io/blender-agent-studio/comparisons/)
  11. A reading room built with Claude Code and Sonnet 5.5, rendered from the saved
  12. scene. It is one selected result, not an average: the [paired
  13. examples](https://ifbars.github.io/blender-agent-studio/comparisons/) show runs
  14. with and without the plugin, including failed checks and mixed visual reviews.
  15. ## Quick start
  16. You need [Claude Code](https://code.claude.com) or
  17. [Codex](https://developers.openai.com/codex), [Blender](https://www.blender.org/download/)
  18. (5.2 LTS is the tested version) and [Bun](https://bun.sh) 1.3.5 or newer.
  19. **1. Install the plugin.**
  20. ```bash
  21. # Claude Code
  22. claude plugin marketplace add ifBars/blender-agent-studio
  23. claude plugin install blender-agent-studio@blender-agent-studio
  24. # Codex
  25. codex plugin marketplace add ifBars/blender-agent-studio
  26. codex plugin add blender-agent-studio@blender-agent-studio
  27. ```
  28. **2. Check your setup.** Start a new Claude Code session or Codex task and ask:
  29. > Check my Blender Agent Studio setup.
  30. The agent runs `blender_check_setup`. It finds Blender, saves and reopens a tiny
  31. scene, renders a small preview image, and tells you what to fix if a step fails.
  32. It never opens your own files. Usually Blender is found
  33. automatically; if not, see [point it at Blender](#point-it-at-blender).
  34. **3. Make something.**
  35. > Use Blender Agent Studio to build a walnut desk lamp. Give it warm lighting,
  36. > render it from two angles, and save the .blend and Python source.
  37. You get an editable `.blend`, the Python that built it, and two renders. Open
  38. the images and judge the lamp yourself: the automated checks catch broken
  39. geometry and exports, not taste. See [more to try](#more-to-try) for writing
  40. your own requests.
  41. ## What you can do
  42. - View an open Blender session inline, orbit and zoom, and attach a clicked object to your next message with the optional [Studio Live addon](docs/live-viewport.md).
  43. - Build props, environments, characters, and Geometry Nodes setups.
  44. - Design readable signs, labels and graphic panels as editable 2D artwork, then integrate their materials and supports and review them at the intended distance. See the [signage workflow](plugins/blender-agent-studio/skills/blender-signage-workflow/SKILL.md).
  45. - Optionally record real modeling milestones and deliver a timelapse from the empty/default scene to the completed render. Ask before modeling starts; [capture guide](plugins/blender-agent-studio/skills/blender-rendering-workflow/references/modeling-timelapse.md).
  46. - Gather references from several angles and compare the model's proportions before adding detail.
  47. - Overlay projected geometry on a reference image, with optional silhouette-mask measurements for missing and excess coverage. See [reference modeling](docs/reference-modeling.md).
  48. - Rig and animate models, or work with cloth, smoke, and other simulations.
  49. - Render through your scene's cameras with its lighting intact, or use studio views to inspect a model from every side.
  50. - Download CC0 textures and HDRIs from Poly Haven at 1K, 2K, 4K, or 8K.
  51. - Find Mixamo motion through your browser and import downloaded FBX animations into a new `.blend`. See the [Mixamo workflow](plugins/blender-agent-studio/skills/blender-animation-workflow/references/mixamo.md) for browser requirements and retargeting limits.
  52. - Find and preview Pixabay sound effects through a browser handoff. The tool provides a search URL and workflow; it does not return live results or import audio. See the [MCP integration guide](plugins/blender-agent-studio/skills/blender-mcp-integration/SKILL.md#pixabay-sound-effects-browser-integration).
  53. - Check geometry and exported files, review renders, and repair what doesn't work.
  54. - Query scene parts and evaluated dimensions, check explicit geometry and ground constraints, and compare repairs against preserved SceneIR baselines with the optional Rust runtime.
  55. The plugin includes twelve specialist skills and a local MCP server for
  56. inspection, rendering, and asset downloads. Generated scenes come with Python
  57. source so you can rebuild them and keep making changes. Codex and Claude Code
  58. have bundled installers today; other hosts need compatible skill loading and
  59. local execution; see [portability and host requirements](https://ifbars.github.io/blender-agent-studio/bring-your-agent/).
  60. ## How it works
  61. The skills guide the agent through modeling, rendering, animation, and other
  62. tasks. Blender runs locally to build or inspect the saved scene; you do not need
  63. to keep its interface open. The agent chooses the relevant steps for your
  64. request. The workflows and tools help it:
  65. - Turn the brief into parts, proportions, finish goals, and delivery checks.
  66. Review a graybox before spending time on materials and small details.
  67. - Check geometry, materials, dimensions, and other scene details. For an export,
  68. it can reopen the file in a fresh Blender process to check what survived.
  69. - Render a hero view plus fixed front, back, left, right, and top views. During
  70. repairs, it can use two smaller views for faster feedback before the full check.
  71. - Light diagnostic views with a studio setup scaled to the asset. The `auto`
  72. preset picks a contrasting background from simple material color hints; the
  73. agent still needs to inspect the image and adjust it when the choice fails.
  74. - Render through the scene's own cameras and lighting for beauty images. The
  75. tool caps resolution, samples, and render time. It offers faster `preview`
  76. and higher-quality `final` denoising policies; by default, it preserves the
  77. scene's authored denoising settings. The agent selects the policy for the job.
  78. The `.blend` is the editable result. The Python source records the build steps,
  79. so you can regenerate it or ask the agent to change it later. The [workflow
  80. guide](SKILL.md#route-the-request) explains which specialist skills apply to
  81. each kind of task. Studio views are for inspection and do not replace your
  82. scene's authored lighting in beauty renders.
  83. ## Install
  84. The [quick start](#quick-start) has the install commands. Both hosts install
  85. the same skills, MCP server, and SceneIR tools from this repository. Inside a
  86. Claude Code session, `/plugin marketplace add ifBars/blender-agent-studio` and
  87. `/plugin install blender-agent-studio@blender-agent-studio` do the same as the
  88. terminal commands.
  89. Start a new task or session after installing or updating the plugin. Both hosts
  90. pick the relevant skill from a plain request. To name one, use
  91. `$blender-agent-studio:blender-modeling-workflow` in Codex or
  92. `/blender-agent-studio:blender-modeling-workflow` in Claude Code.
  93. ### Point it at Blender
  94. The plugin uses the first Blender it finds:
  95. 1. A `blenderPath` given to a tool, or `--blender` on the command line.
  96. 2. The `BLENDER_EXECUTABLE` environment variable.
  97. 3. `blender` on your `PATH`.
  98. 4. Standard install locations: the official installers on macOS
  99. (`/Applications`) and Windows (`Program Files\Blender Foundation`), Steam,
  100. and on Linux Snap, Flatpak, and archives unpacked in your home folder or
  101. `/opt`. When several are installed, it prefers 5.2 LTS.
  102. A configured path that is wrong is reported, never silently replaced. For any
  103. other location, set `BLENDER_EXECUTABLE` to the executable itself, not its folder:
  104. ```powershell
  105. $env:BLENDER_EXECUTABLE = "C:\path\to\Blender\blender.exe"
  106. ```
  107. ```bash
  108. export BLENDER_EXECUTABLE="/Applications/Blender.app/Contents/MacOS/Blender"
  109. ```
  110. Launch your CLI agent from the terminal where you set the variable, or configure
  111. your desktop host's environment; a new conversation may not inherit shell
  112. changes. `blender_version` reports which executable was found and how.
  113. ### Check from a terminal
  114. The same setup check runs without an agent. From a repository checkout or the
  115. installed plugin directory:
  116. ```bash
  117. bun run doctor
  118. ```
  119. It saves and reopens a tiny scene, renders a 128px Cycles preview on CPU, and
  120. tries a 64px EEVEE render. It needs no API key, GPU, downloads, or Rust, and it
  121. keeps the `.blend`, previews, logs, and a JSON report in a new temporary folder.
  122. A failed check exits nonzero. An EEVEE warning means Cycles works but the studio
  123. inspection views need OpenGL, which headless Linux machines may lack. Use
  124. `--blender "/path/to/blender"` to override discovery or `--output-dir NEW_DIRECTORY`
  125. to keep the evidence somewhere specific. See [setup troubleshooting](docs/development.md#setup-troubleshooting)
  126. if a check fails.
  127. ### Optional and alternative installs
  128. For the optional scene-understanding tools, build the Rust runtime in the
  129. installed plugin directory with `bun run setup:runtime`. See
  130. [scene understanding](docs/scene-understanding.md) for setup, examples and
  131. measurement limits. The other tools do not require Rust.
  132. <details>
  133. <summary>Update an existing GitHub installation</summary>
  134. Codex:
  135. ```bash
  136. codex plugin marketplace upgrade blender-agent-studio
  137. codex plugin add blender-agent-studio@blender-agent-studio
  138. ```
  139. Claude Code:
  140. ```bash
  141. claude plugin marketplace update blender-agent-studio
  142. claude plugin update blender-agent-studio@blender-agent-studio
  143. ```
  144. </details>
  145. Prefer skills only? See the [alternative installation options](docs/development.md#skills-only-installation)
  146. and [browse the workflows on skills.sh](https://skills.sh/ifbars/blender-agent-studio).
  147. ## More to try
  148. Include the style, dimensions, and intended use when they matter:
  149. > Build a 30 cm stylized brass lantern for a mobile game. Export a GLB and
  150. > check that it imports correctly.
  151. > Here is `desk.blend`. Inspect it from every side, list what looks wrong, and
  152. > fix the worst problem without changing anything else.
  153. For a game asset, ask for a GLB export and an import check. For a render, you
  154. can specify a camera angle, lighting, or reference image. For a second review,
  155. ask the agent to check the result from multiple views.
  156. ## How well does it work?
  157. In five fresh, matched pairs covering a lantern, lever press, and animated
  158. drawbridge, the plugin's guided workflow passed the technical gate five times;
  159. the agent without it failed five times. Three blinded visual judges preferred
  160. the plugin asset in four of the five pairs. On one lantern repeat, all three
  161. preferred the baseline's appearance even though its geometry failed the
  162. technical gate. The plugin used more reported tokens. Lantern build time was
  163. about even across three pairs; the press and drawbridge plugin runs took about
  164. twice as long. See the [current paired evidence](docs/plugin-quality-evidence.md)
  165. for scores, controls, and defects.
  166. These results show a quality gain for delivery checks on the tested prompts,
  167. with less consistent visual gains. Five pairs cannot give a reliable success
  168. rate for arbitrary prompts, models, or art styles. The three judges in each
  169. pair reviewed the same two assets; their votes are not separate generations.
  170. The comparison used the plugin's skills without its optional MCP tools, so it
  171. does not measure the extra benefit of those tools. An [earlier four-task
  172. comparison](plugins/blender-agent-studio/skills/blender-agent-benchmark/references/validated-results.md)
  173. also favored the plugin's final runs, but a harder integrated task had mixed
  174. results. Plugin revisions have shown [both gains and
  175. regressions](docs/quality-development.md). Review the result yourself,
  176. particularly its shape, materials, animation, and exported files.
  177. The five pairs above ran in Codex. The [published gallery](https://ifbars.github.io/blender-agent-studio/comparisons/)
  178. now retains 31 pairs, including later scene comparisons with Sonnet 5.5 and
  179. Opus 5.5 in Claude Code, alongside the Codex models. The [scene report](docs/scene-comparison-2026-10-04.md)
  180. records their controls, scores, visual votes, and missing reviews. Those scene
  181. results are mixed; the selected reading-room image above does not establish a
  182. general visual advantage. Each pair has one generation per condition, so the
  183. gallery is evidence to inspect rather than a general success rate.
  184. The [earlier Claude Code lantern samples](docs/plugin-quality-evidence.md#claude-code-samples)
  185. had no baseline and remain separate from those paired scene comparisons.
  186. Keep each result tied to its tested host, model, task, and plugin revision.
  187. ## Support development
  188. If Blender Agent Studio helps you build or inspect scenes, consider supporting
  189. its maintainer through [GitHub Sponsors](https://github.com/sponsors/ifBars) or
  190. [Ko-fi](https://ko-fi.com/ifbars). Contributions help sustain the time spent on
  191. Blender and agent compatibility, reproducible examples, bug fixes, and benchmark
  192. runs that report failures as well as improvements.
  193. The plugin stays free, MIT-licensed, and runs Blender locally. Sponsorship is
  194. optional and does not purchase priority support or feature commitments. Sharing
  195. a scene, reporting a reproducible bug, or improving the docs also helps.
  196. ## Star history
  197. <a href="https://www.star-history.com/?repos=ifBars%2Fblender-agent-studio&type=date&legend=top-left">
  198. <picture>
  199. <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=ifBars/blender-agent-studio&type=date&theme=dark&legend=top-left" />
  200. <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=ifBars/blender-agent-studio&type=date&legend=top-left" />
  201. <img alt="Blender Agent Studio star history chart" src="https://api.star-history.com/chart?repos=ifBars/blender-agent-studio&type=date&legend=top-left" />
  202. </picture>
  203. </a>
  204. ## Contributing
  205. Found a bug? [Open an issue](https://github.com/ifBars/blender-agent-studio/issues)
  206. with your Blender version, what you asked for, and what happened. A render or
  207. error log helps.
  208. Made something with the plugin? [Share an example](https://github.com/ifBars/blender-agent-studio/issues/new?template=share-an-example.yml)
  209. with your prompt, agent/model, Blender version, and a render. If you want it
  210. featured in the docs, say so and include the build script when you can. Only
  211. share files you have permission to publish.
  212. For code changes, see the [development guide](docs/development.md) and
  213. [repository instructions](AGENTS.md). Keep generated models and benchmark output
  214. out of commits. Review unfamiliar Blender scripts before running them; see
  215. [security notes](SECURITY.md).
  216. ## Credits and license
  217. [MIT](LICENSE). Powered by [Poly Haven](https://polyhaven.com), whose assets are
  218. [CC0](https://polyhaven.com/license).
  219. This is an independent project, not affiliated with or endorsed by the Blender
  220. Foundation or Poly Haven. See [third-party notices](THIRD_PARTY_NOTICES.md).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.