Script Launcher
Manage and run Python scripts from multiple root folders.
Script Launcher lets you organize and run Python scripts directly from the 3D Viewport sidebar — keeping your workflow entirely inside Blender.
⚠️WARNING
This add-on runs Python scripts directly inside Blender. Always review a script's contents before executing it, and never run scripts from sources you do not trust.
Features
- Multiple root folders — Register as many script directories as you need. Personal scripts, project tools, and shared libraries can all coexist in a single panel.
- Folder tree view — Scripts are displayed in a collapsible tree that mirrors your directory structure. Expand only what you need, collapse the rest.
- Run scripts instantly — Execute any
.pyfile with one click. - Open in Blender's Text Editor — Load a script into Blender's built-in editor for quick review or editing. No context-switching required.
- Open in file manager — Jump to the script's location on disk in one click.
- Persistent UI state — Expand/collapse states survive list refreshes and file reloads.
- Search scripts — Real-time filtering by name. Type in the input field next to the 🔍 icon, click × to undo.
Usage
Access via 3D Viewport → Sidebar (N key) → Script Launcher tab.
| Button | Action |
|---|---|
| 🔄 | Refresh the script list |
| 📄 | Open selected script in Text Editor |
| 📂 | Open the selected item's folder in File Manager |
| ⚙️ | Open add-on Preferences |
| Run Script | Execute the selected .py file |
Click ▶ / ▼ next to a subfolder to expand/collapse it.
Settings
Configure via Edit → Preferences → Add-ons → Script Launcher.
- Panel Category — Change the Sidebar tab name (default:
Script Launcher) - Script Roots — Add/remove root folders with
+/-buttons; edit path and display name in the box below the list
On first install, the scripts/ folder inside the add-on directory is registered automatically.
What's New
1.2.2 June 19th, 2026
- Script execution now uses Blender's built-in
bpy.ops.script.python_file_runoperator instead ofexec(), complying with the Extensions platform policy on dynamic code execution. - No change in behavior: scripts still run with
__name__ == "__main__"and__file__set (same as the Text Editor's Run Script), and imported modules still won't create__pycache__in your script folders.
Very useful, thanks for the extension! As a humble proposal: To save precious space in the N-panel, I suggest changing the label from "Script Launcher" to something shorter, like "Scripts" or "Python". (It's already implied that you can launch your scripts so I think it might be beneficial to shorten it.)