vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(blender): desktop Blender + MCP registration per working session, not per task (Prime 2026-09-28)

Browse Source
This commit is contained in:
vh
2026-09-28 16:36:44 -07:00
parent 85f8a3a072
commit ea5d8dfd4e
4 changed files with 24 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/fleettools/blender.md
+7 -4
View File
@@ -11,7 +11,7 @@ runs only while in use, and this access ends if a big seat moves onto the card.
| You are… | Use | Shape |
|---|---|---|
| a script or CLI caller (renders, conversions) | `scripts/blender-run` | one-shot `docker run --rm`: no desktop, gone when Blender exits |
| an agent building scenes interactively | `scripts/blender-mcp` (MCP, per task) | a GUI Blender plus the mcp-for-blender add-on; `up` / `status` / `down` |
| an agent building scenes interactively | `scripts/blender-mcp` (MCP, per working session) | a GUI Blender plus the mcp-for-blender add-on; `up` / `status` / `down` |
Both scripts are in `/home/lkraven/development/eshpfi-management/scripts/` and run from nh3-dev,
reaching fv-ml1 as `infra-ops@10.251.50.54` over ssh. **No HTTP API** and no openapi.json.
@@ -69,8 +69,11 @@ scripts/blender-run -- --python-expr 'import bpy; print(bpy.app.version_string)'
## blender-mcp (agents)
Register it **per task**, never user- or project-wide (Prime, 2026-09-27):
Bring it up **once per working session**, never always-on, and never register it user- or
project-wide (Prime, 2026-09-28, superseding the 2026-09-27 per-task rule). At session start:
`scripts/blender-mcp up`, wait for `status` to say answering, then
`claude mcp add blender -- /home/lkraven/development/eshpfi-management/scripts/blender-mcp`.
Then run `scripts/blender-mcp up`, wait for `status` to say answering, work, and run `down`
when finished. Safe mode is on (no os/open/network in agent code), so the startup hook has
At session end: `claude mcp remove blender` (the default local scope persists for the
directory) and `scripts/blender-mcp down`. There is one GUI and one scene, so MCP work
serializes fleet-wide; parallel work goes through blender-run. Safe mode is on (no os/open/network in agent code), so the startup hook has
already pointed Cycles at OptiX. Save to `/work/…`. Details and traps are in the stack README.