Blender forbids Python threads. So my AI add-on talks to itself through two JSON files
The pivot I spent the last months building a local multi-agent CLI code generator - planner → coder → tester → executor → reviewer, running on open models via Ollama. It closed the loop: it wrote code, ran it, tested it, and fixed it. It worked. And that's exactly the problem: it solved a problem I
The pivot I spent the last months building a local multi-agent CLI code generator - planner → coder → tester → executor → reviewer, running on open models via Ollama. It closed the loop: it wrote code, ran it, tested it, and fixed it.
It worked. And that's exactly the problem: it solved a problem I don't have. Writing code for files on disk is a solved niche - I was competing with every other code-gen tool for a user who already has one.
What I actually do all day is 3D. So the project became something else: an AI assistant that lives inside Blender and holds real tools for working with models, not just a text box that emits code.
What works right now The add-on is called Game Asset Assistant, targets Blender 4.2+, and ships as a proper extension zip.
Docked in the 3D Viewport sidebar (N → AI tab) Also opens as a standalone floating window with Ctrl+Alt+A Streamed responses, message history, stop/clear buttons It knows your scene
Every request carries a compact snapshot injected into the system prompt:
Blender 4.2.0 Scene: Scene | fps=24 | units=METRIC | render=CYCLES Objects: 12
Expand Zalogin Aleksei Zalogin Aleksei Zalogin Aleksei Follow QA Automation Engineer with 4 years of experience, from manual testing and team leadership to building automation frameworks from scratch. My core strength is API and backend testing of microservices Email sleepyboy906sb@gmail.com Location Moscow Work QA Automation Engineer Joined Aug 25, 2026 • Oct 19 Dropdown menu Copy link Hide github.com/SickSect/BlenderAgent