@volter/editor-blender 0.1.22 → 0.1.24

package/contributions/blender-outliner-authoring.ts

@@ -831,6 +831,26 @@ function py(name: string): string {
   return JSON.stringify(name);
 }
 
+/** Blender's own name for each operator, as its undo history labels the step (`ot->name`). */
+const operatorNames = new Map<string, string>();
+
+/**
+ * THE STEP'S LABEL IS THE OPERATOR'S OWN NAME, the one Blender's Edit menu shows: Add › Cone is
+ * "Undo Add Cone", not "Undo Blender Python". Asked of Blender, not kept in a table here, because
+ * its names do not follow the menu rows (a Point light is "Add Light").
+ */
+async function operatorLabel(body: string): Promise<string> {
+  const id = /bpy\.ops\.([a-z_]+\.[a-z0-9_]+)\(/.exec(body)?.[1];
+  if (id === undefined) return 'Blender Python';
+  const known = operatorNames.get(id);
+  if (known !== undefined) return known;
+  const answer = await blenderExecute(`import bpy\nprint(bpy.ops.${id}.get_rna_type().name)`, false);
+  const name = answer.error === null ? answer.result.trim() : '';
+  if (name === '') return 'Blender Python';
+  operatorNames.set(id, name);
+  return name;
+}
+
 /**
  * RUN ONE OPERATOR AND SAY WHICH OBJECTS IT MADE.
  *
@@ -849,7 +869,7 @@ function py(name: string): string {
  */
 async function runBlenderOperator(
   body: string,
-  label = 'Blender Python',
+  label?: string,
 ): Promise<{ readonly made: readonly string[]; readonly error: string | null }> {
   const code = [
     'before = {o.name for o in bpy.data.objects}',
@@ -857,7 +877,7 @@ async function runBlenderOperator(
     'made = [o.name for o in bpy.data.objects if o.name not in before]',
     'print("\\n".join(made))',
   ].join('\n');
-  const answer = await blenderExecute(code, true, label);
+  const answer = await blenderExecute(code, true, label ?? (await operatorLabel(body)));
   // THE ENGINE'S REFUSAL, VERBATIM. `session.py::execute` answers with the
   // traceback in `error` rather than raising, and a paraphrase here is how a
   // refusal becomes a shrug.

package/contributions/blender-runtime.document.tsx

@@ -61,6 +61,12 @@ import { BlenderObjectModeHeader } from './blender-header-menus';
 import { blenderOutlinerAuthoringFor, createBlenderOutlinerAuthoring } from './blender-outliner-authoring';
 import { blenderSkin } from './blender-runtime-skin';
 import { areaSplit, subscribeAreaSplit } from '../src/area-split';
+import {
+  documentSecondAreaHeader,
+  setDocumentSecondArea,
+  subscribeDocumentAreas,
+} from '@volter/editor-sdk/kit/document-areas';
+import { createPortal } from 'react-dom';
 import { onViewportStages, viewportStages } from '@volter/editor-threejs/viewport-door';
 import {
   object3DDocumentSession,
@@ -266,7 +272,7 @@ function BlenderModelViewport(props: ToolContributionProps) {
         <BlenderViewportArea {...props} view={view} main />
       </div>
       {second && (
-        <div style={{ ...area, marginTop: 24 + AREA_HEADER }} data-testid="blender-second-area">
+        <div style={area} data-testid="blender-second-area">
           <BlenderViewportArea {...props} documentId={`${documentId}#area-2`} view={second.view} main={false} />
           <SecondAreaChrome documentId={documentId} areaId={`${documentId}#area-2`} notify={props.notify} />
         </div>
@@ -281,9 +287,18 @@ function BlenderModelViewport(props: ToolContributionProps) {
  * header controls its own stage registered, so its shading cells change this area and not the
  * other.
  */
-/** The height of an area's own header row: the document strip's (`volter-dock-document-toolbar`). */
-const AREA_HEADER = 26;
-
+/**
+ * THE SECOND AREA'S OWN HEADER AND SHELF, as each of Blender's areas has them.
+ *
+ * The area is declared to the host as the document's second area
+ * (`@volter/editor-sdk/kit/document-areas`). Its HEADER stands in the document's header row over
+ * this area: the host reserves this area's width at the row's trailing edge, so the first area's
+ * header ends where the first area does, and this renders into the region it draws there: the
+ * editor menus (their View ▸ Area ▸ Close Area closes this area), then THIS area's view, shading
+ * and helpers, the header controls its own stage registered, so its shading cells change this
+ * area and not the other. Its SHELF is an element the host fills with its own tool strip: the
+ * tools belong to the workspace in Blender, not to an area, so both shelves are the one strip.
+ */
 function SecondAreaChrome({
   documentId,
   areaId,
@@ -294,24 +309,40 @@ function SecondAreaChrome({
   readonly notify: ToolContributionProps['notify'];
 }) {
   useSyncExternalStore(subscribeDocumentViewports, documentViewportsVersion, documentViewportsVersion);
+  const header = useSyncExternalStore(subscribeDocumentAreas, () => documentSecondAreaHeader(documentId));
   const HeaderControls = documentViewport(areaId)?.HeaderControls;
+  const shelfRef = useRef<HTMLDivElement>(null);
+  // THE RESERVED WIDTH IS THIS AREA'S: from its stage's left edge (the area bleeds 12 px past its
+  // box, as the stage does) to the row's end, kept as the split or the window moves.
+  useEffect(() => {
+    const shelf = shelfRef.current;
+    const area = shelf?.parentElement;
+    if (!area) return;
+    const measure = (): void =>
+      setDocumentSecondArea(documentId, { headerWidth: area.getBoundingClientRect().width + 12, shelf });
+    measure();
+    const observer = new ResizeObserver(measure);
+    observer.observe(area);
+    return () => {
+      observer.disconnect();
+      setDocumentSecondArea(documentId, null);
+    };
+  }, [documentId]);
   return (
     <>
-      {HeaderControls && (
-        <div
-          className="volter-dock-document-toolbar"
-          data-testid={`document-header:${areaId}`}
-          style={{ position: 'absolute', top: -12 - AREA_HEADER, height: AREA_HEADER, left: -12, right: -12 }}
-        >
-          {/* Blender's area header opens on the same editor menus; they act on the document. */}
-          <div className="volter-dock-document-toolbar-own">
+      <div ref={shelfRef} className="volter-dock-document-shelf" role="toolbar" aria-orientation="vertical" aria-label="Document tools" />
+      {header &&
+        createPortal(
+          <div className="volter-dock-document-toolbar-own" data-testid={`document-header:${areaId}`} style={{ display: 'flex', alignItems: 'center' }}>
             <BlenderObjectModeHeader documentId={documentId} notify={notify} />
-          </div>
-          <Suspense fallback={null}>
-            <HeaderControls documentId={areaId} />
-          </Suspense>
-        </div>
-      )}
+            {HeaderControls && (
+              <Suspense fallback={null}>
+                <HeaderControls documentId={areaId} />
+              </Suspense>
+            )}
+          </div>,
+          header,
+        )}
     </>
   );
 }

package/contributions/blender-screenshot.menu.ts

@@ -0,0 +1,32 @@
+/**
+ * Window ▸ Save Screenshot (Editor)… — Blender's own row (`TOPBAR_MT_window`, `screen.screenshot_area`),
+ * the person's door to the photograph an agent takes with `get_viewport_screenshot`.
+ *
+ * Blender asks for a path in its file browser; the files door has no file picker, so the picture
+ * goes to the project's `screenshots/` folder and the console says which file it is. Like every
+ * photograph of the document it flashes the document and shows itself in the corner.
+ */
+import type { MenuContribution } from '@volter/editor-sdk/chrome';
+import { editorHost } from '@volter/editor-sdk/host';
+import { announcePhotograph } from '@volter/editor-sdk/kit/photograph-notice';
+
+export const point = 'workspace.menu';
+
+export const menu: MenuContribution = {
+  menu: 'window',
+  items: [
+    {
+      id: 'blender-save-screenshot-editor',
+      label: 'Save Screenshot (Editor)…',
+      testId: 'menu-save-screenshot-editor',
+      execute: async () => {
+        const host = editorHost();
+        const capture = await host.documents.captureActive();
+        announcePhotograph(capture.base64);
+        const path = `screenshots/screenshot-${new Date().toISOString().replace(/[:.]/g, '-')}.png`;
+        await host.files.write(path, Uint8Array.from(atob(capture.base64), (c) => c.charCodeAt(0)));
+        host.console.log(`Saved the screenshot to ${path}.`, 'blender-screenshot');
+      },
+    },
+  ],
+};

package/host/blender-runtime-host.ts

@@ -1033,7 +1033,7 @@ export function blenderRuntime(): BlenderRuntime {
     // resolve, and `blender_tools.py` deliberately keeps a failing SCRIPT's
     // traceback out of it.
     // biome-ignore lint/suspicious/noConsole: the Blender worker's log is page output by design.
-    log: (level, text) => (level === 'error' ? console.error : console.log)(`[blender] ${text}`),
+    log: (level, text) => console[level](`[blender] ${text}`),
   });
   const session = runtime;
   // MEASUREMENT, PUBLISHED THE MOMENT THE SESSION EXISTS. The worker cannot say

package/node/blender-mcp.ts

@@ -300,9 +300,14 @@ export async function serveBlenderMcp(
   command: string,
 ): Promise<void> {
   const runtimeIdentity = `Blender ${blenderBundle.blender} (source ${blenderBundle.source}), compiled to WebAssembly and running headless in the editor tab; three.js takes its photographs. Factory bpy.context.scene.render.engine: '${blenderBundle.factoryEngine}'. Documents are .blend. save_as_mainfile records the actual saved path in bpy.data.filepath; open_mainfile reopens it.`;
+  // THE PHOTOGRAPH STAYS IN THE EDITOR. An agent asked to "take a photograph" with no word on where
+  // it goes rendered one, wrote it into the project and ran the OS `open` on it: Preview started
+  // outside the editor. The editor already shows a picture as one of its documents.
+  const photographs = `A photograph is shown to the person in the editor, never in another app: get_viewport_screenshot returns one, and an image file written inside the project opens as an editor document with \`npx ${command} eval 'editor.openAsset("<project-relative path>")'\`. Do not run the OS \`open\` on it.`;
+  const instructions = `${runtimeIdentity}\n${photographs}`;
   const tools = (blenderTools as ToolShape[]).map((tool) =>
     tool.name === 'execute_blender_code'
-      ? { ...tool, description: `${runtimeIdentity}\n${tool.description}` }
+      ? { ...tool, description: `${instructions}\n${tool.description}` }
       : tool,
   );
   const defaults = blenderDefaults as Record<string, string>;
@@ -317,7 +322,7 @@ export async function serveBlenderMcp(
     { name: 'BlenderMCP', version: BLENDER_MCP_VERSION },
     {
       capabilities: { tools: {}, prompts: {} },
-      instructions: runtimeIdentity,
+      instructions,
     },
   );
 

package/package.json

@@ -2,7 +2,7 @@
   "name": "@volter/editor-blender",
   "author": "Volter AI, Inc.",
   "license": "AGPL-3.0-only AND GPL-3.0-or-later",
-  "version": "0.1.22",
+  "version": "0.1.24",
   "publishConfig": {
     "access": "public"
   },
@@ -36,6 +36,7 @@
       "./contributions/blender-timeline.document.tsx",
       "./contributions/blender-uv-editor.document.tsx",
       "./contributions/blender-runtime.document.tsx",
+      "./contributions/blender-screenshot.menu.ts",
       "./contributions/blender-version.status.tsx",
       "./contributions/blender.command.ts",
       "./contributions/blender.environment.ts",
@@ -69,15 +70,16 @@
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "1.30.0",
-    "@volter/blender-engine": "0.1.20",
-    "@volter/editor-threejs": "0.5.82",
+    "@volter/blender-engine": "0.1.22",
+    "@volter/editor-threejs": "0.5.84",
     "zod": "^4.3.6"
   },
   "peerDependencies": {
-    "@volter/editor-sdk": "0.5.82",
-    "@volter/editor-live": "0.5.82",
-    "@volter/editor-project": "0.5.82",
+    "@volter/editor-live": "0.5.84",
+    "@volter/editor-project": "0.5.84",
+    "@volter/editor-sdk": "0.5.84",
     "react": "^19.0.0",
+    "react-dom": "^19.0.0",
     "three": "^0.180.0",
     "vite": "^6.4.3"
   },

package/src/area-split.ts

@@ -44,3 +44,4 @@ export function subscribeAreaSplit(listener: () => void): () => void {
     listeners.delete(listener);
   };
 }
+