Configuration reference

Blender Development separates settings that belong to one project from settings shared by the PyCharm application.

Project settings

Open Project Blender Manager to edit these values.

Setting	Purpose
Blender path	Executable or application bundle used for launches.
Blender version	Target used for compatibility defaults and API stubs.
Add-on name	Runtime identity; spaces and hyphens are normalized to underscores.
Source folder	Source root loaded by Blender.
Run arguments	Additional Blender command-line arguments.
Log level	Value passed to Blender’s --log-level option.
Reload on save	Reloads the add-on after file saves during Debug sessions.
Just my code	Limits debugger stepping to project code.
Extension repository	Repository name used for Blender extensions.
Environment variables	Project launch variables; these override global duplicates.
Script directories	Additional add-on roots or directories containing add-on roots.

The project also records the installed API-stub requirement so it can offer an update after the target Blender version changes.

Application settings

Open Settings > Tools > Blender Development to edit settings shared across projects.

Setting	Purpose
Blender installation root	Extra root included during installation discovery.
Log path	Destination for plugin logs.
Global environment variables	Base variables applied to every Blender launch.

Detected Blender installations are cached after a scan. Download and code-completion path fields may also appear in persisted settings, but their managed installation workflows are not implemented in the current pre-release.

Environment precedence

For each launch, the plugin applies global environment variables first and project variables second. A project value therefore wins when both scopes define the same key.