blender-dev

Development-only diagnostics for Blender add-ons and adapter debugging.

Prefer typed domain skills for scene authoring. Use this skill when you need to inspect add-on state, attach a checkout to sys.path, reload development modules, run a named diagnostic check, inspect structured UI metadata, or start an optional debugpy listener. Code execution helpers can run arbitrary Python inside Blender and should be used only for explicit development or test flows.

Add-on lifecycle

list_addons / get_addon_status / enable_addon / disable_addon cover add-ons Blender already knows about. These three cover the rest: