name: blender-dev-start-terminal
description: Audit what Blender Development executes for Blender: Start and run an equivalent Blender 5.0 terminal flow without relying on the VS Code command.
Blender Development Start (Terminal)
Goal
Understand and reproduce Blender: Start for Blender 5.0 from terminal commands/scripts.
Source of truth
out/extension.js
COMMAND_startdelegates to launch helpers.
out/blender_executable.js
- Builds process execution:
blender.exe --python <launch.py>. - Exports env vars:
ADDONS_TO_LOAD,EDITOR_PORT,VSCODE_*.
pythonFiles/launch.py
- Parses
ADDONS_TO_LOAD, then callsblender_vscode.startup(...).
pythonFiles/include/blender_vscode/__init__.py
- Installs requirements, links addon/extension path, starts communication/debug server, registers dev operators, enables addon.
Workflow
- Confirm Blender Development extension version/path in the user profile.
- Confirm workspace addon path and module name.
- Choose one terminal replication mode:
direct(recommended): load/register addon directly for interactive work.blender-development(parity mode): run the extensionlaunch.pywith the same env contract.
- Execute
tools/blender_dev_start.pywith Blender 5.0 path. - Verify addon loaded in console/logs.
Commands
Direct mode (recommended, no VS Code server dependency):
& "C:\Program Files\Blender Foundation\Blender 5.0\5.0\python\bin\python.exe" tools\blender_dev_start.py --mode direct --blender-exe "C:\Program Files\Blender Foundation\Blender 5.0\blender.exe"
Parity mode (matches Blender Development startup contract):
& "C:\Program Files\Blender Foundation\Blender 5.0\5.0\python\bin\python.exe" tools\blender_dev_start.py --mode blender-development --editor-port 17342 --blender-exe "C:\Program Files\Blender Foundation\Blender 5.0\blender.exe"
Validation
- Startup log includes:
[Lime Pipeline] Loading addon from: ... addon_utils.check("lime_pipeline")returns loadedTrue.- No path corruption in
%APPDATA%\Blender Foundation\Blender\5.0\scripts\addons\lime_pipeline.