DeepBlend Studio

Your Blender studio, inside DeepSeek Harness.
Start with a product recipe or your own model. Shape the scene. Compare real renders. Deliver the result.

English · 简体中文

Quick start · See the workbench · Documentation · Latest release · Contribute

Latest stable 0.9.0 links the mast, joints and arm root for a 250 mm lamp shade, preserves legacy projects and independent edits, and adds source-bound native part dimensions to the workbench.

Quick start

With Node.js 22.23.3 or newer, DSH 0.1.5-rc.2, pnpm and Blender 5.2.1 ready:

dsh plugin --profile web add @deepblend/dsh-blender-bundle
dsh web

Restart an already running dsh web after installation. In a new session, choose the DeepBlend Studio
preset and open Blender in the sidebar. Both the workbench and agent presets are included.

First time setting up Blender or DSH? Follow the English / Chinese quick-start guide.
FFmpeg and ffprobe are needed when encoding an MP4. Install them with brew install ffmpeg on macOS,
sudo apt install ffmpeg on Debian/Ubuntu, or winget install ffmpeg on Windows. You can create and render scenes before adding them.

Other install paths and upgrading an existing installation

Prebuilt bundle:

dsh plugin --profile web add https://github.com/pearjelly/deep-blend/releases/latest/download/deepblend-bundle.tgz

Current source tree:

dsh plugin --profile web add 'github:pearjelly/deep-blend#path:/packages/deepblend/bundle'

The quoted #path: form keeps the shell from treating # as a comment. Source installs may need the build approval
reported by DSH; follow that message. pnpm must be on PATH for every install route.

Already installed? Replace the existing registration before adding the new package, then restart dsh web:

dsh plugin --profile web remove @deepblend/dsh-blender-bundle
dsh plugin --profile web add @deepblend/dsh-blender-bundle

See the installation and upgrade guide for configuration and storage details.

New case: Night Shift

Created through DeepSeek Harness with the installed deep-blend 0.5.0 plugin: Blender’s official CHARGE Packbot, a new industrial set, lighting and six seconds of camera motion. 79 mesh parts, 511,595 polygons, 19 packed images; 1080p / 24 fps / 144 actually rendered frames. An independent DSH replay matched the scene digest; the frame-72 preview differed by at most 1/255 per channel.

播放视频 / Watch · 复现指南 / Replay guide · 完整复现素材 / Replay inputs

The robot uses the source asset’s static frame-1 pose; the film demonstrates the new set and camera motion. CHARGE Packbot © Blender Studio / Blender Foundation — CC-BY; new scene code is MIT. The promotional edit only adds titles and attribution. Release 0.8.1 includes replay inputs under examples/charge-study/; the guide pins the verified 0.5.0 environment.

Real work: light and material

Three product studies made with the locally installed DeepBlend plugin: amber glass, a champagne-metal lamp and a speaker with a physical woven grille. Each includes a high-resolution hero, a material close-up and a 6-second / 1080p / 24 fps camera animation.

琥珀时间 · Amber Atlas	金色暮光 · Solstice	织声 · Nocturne

Play MP4	Play MP4	Play MP4

The inline previews sample the actual films at 12 fps; the MP4s retain all 144 rendered frames at 24 fps. Click a preview for its 2560×1440 still.

Open the gallery · Scene sources and rebuild · Render provenance · Official Blender visual references

The scenes and output come from editable SceneSpec and actual rendering. Official Blender examples informed the lighting and material direction; no official demo model, texture or movie frame is used in these three product studies.

Make something concrete

These are actual Blender renders, with reproducible source scenes and image provenance.
The cup image comes from the recorded tutorial.

Metal task lamp	Glass and ceramic
Cycles render of a metal task lamp	Cycles render of a hollow glass vessel and ceramic tray
Desktop speaker	Glazed handled cup
Cycles render of a desktop speaker

Pick a recipe, adjust its exposed color, roughness and exposure, and create a project with a rendered preview.
Creation errors keep your inputs and offer repair guidance and explicit retry. If a saved project's reply was lost, retry recovers it without creating another project. Browser creation drafts can be explicitly continued after reload or reopening, with separate drafts for each page.
Or start with your own glTF, GLB or OBJ model and its external textures.

Keep a setup you like: reuse photography from a saved work and version, apply its camera settings and lights to a draft, then inspect and save. Models and materials stay with the destination work.

Follow a complete creation: the glazed cup walkthrough changes height,
compares clay views, adjusts the glaze and key light, and delivers a frame. Its handle roots still show visible
bulges; the tutorial preserves that limitation. The recipe has no animation tracks, so adding frames does not create turntable motion.

Choose how you work

Start here	What you do	Guide
Create in the workbench	Use a recipe or import a model; edit dimensions, materials, cameras and lights	Workbench guide
Work with an agent	Describe a scene, inspect previews and make bounded changes with the DeepBlend Studio preset	Agent creation guide
Build your own recipes or tools	Validate scene documents and content through the typed public SDK	Authoring SDK

The agent preset provides 18 model-visible tools for scenes, assets, previews, visual review and delivery.
You can use the gallery and manual workbench controls for your first creation before asking an agent to edit it.

Try this in a session using the DeepBlend Studio preset:

List the available product recipes. Show me the glazed handled cup and its parameters before creating anything.
After I choose the values, create a preview. Keep later material and lighting changes in separate revisions.

This is an example request, not a recorded run. Use the tool guide to inspect what each operation does.

From a starting point to a saved result

Step	In the studio	What stays inspectable
Create	Start from a recipe or upload a model bundle, texture or environment map	Recipe version, original resource paths and source bytes
Refine	Edit shape, bevels, arrays, local materials and procedural surface grain; adjust cameras and lights	A new saved scene revision for each accepted change
Review	Compare previews, inspect fixed-view beauty/clay images, and save reference images with a design goal	The actual image, camera, frame and render conditions
Deliver	Render PNG frames and encode an MP4; cancel or resume a job	Frame progress, actual render settings and delivery provenance

Assets · Modeling · Photography · Inspection · Recovery

The 0.9.0 public three-route check used paired DSH 0.1.5-rc.2 and pnpm 9.15. For source/npm installation, the temporary profile explicitly allowed workspace-root installation and used peers supplied by the installed DSH; fetching newer peers had failed on dsh-type-meta. These options apply only to this command:

npm_config_ignore_workspace_root_check=true npm_config_auto_install_peers=false dsh plugin --profile web add @deepblend/dsh-blender-bundle

The prebuilt tarball was independently installed. Keep DSH's explicit source-build approval prompts.

See the workbench

The following images were captured from a running DSH workbench, Chrome and Blender by
deepblend/tools/capture-docs-images.mjs. They are product screenshots and render output, separate from the illustrated brand banner above.

Actual Blender workbench showing a project, revision and scene controls

Preview comparison and the rendered contact sheet

The comparison displays actual saved previews from two revisions; image and source hashes are retained in the capture manifest.

Actual before/after revision previews with their own image digests and timestamps

The contact sheet combines animation sample frames with additional inspection viewpoints.

Actual seven-view Blender contact sheet

Why the iteration stays inspectable

Saved history. An accepted edit creates an immutable revision. Restoration moves the current pointer while keeping the intervening history.
Source-led scenes. SceneSpec is the source of truth; .blend is a compiled artifact. Scenes can be rebuilt from the declared inputs and locked resources.
Recoverable delivery. Frame files are checked rather than trusted from a counter. Resume renders missing or invalid frames; complete frames can proceed directly to encoding.
Explicit render budgets. Expensive operations use an approval gate, and the requested scene revision remains attached to the job.
Separate kinds of evidence. Technical measurements and image-backed artistic review are distinct; a higher score does not establish a better-looking result.

Artistic review · Runtime and recovery · Security controls

Documentation by task

I want to…	Start here
Install, configure Blender, or update the plugin	Quick start · Installation
Complete my first creation	Cup walkthrough
Import my own model, textures or environment	Asset library
Tune the shape or photography	Modeling · Camera and light editing
Compare versions and investigate a rough result	Fixed-view inspections · References
Resume a render or recover a saved scene	Recovery
Author a recipe or integrate the SDK	Recipes · Public API
Contribute, reproduce evidence or inspect limitations	Contributing · Acceptance register

Browse the documentation hub. Detailed operation manuals are primarily in Chinese;
the quick-start guide and public authoring entry are available in English.

Questions before you start

Do I need an AI model to create my first project?

The workbench gallery, editing controls and local renders can be used directly. Agent conversation and model-based visual review use the model configured in DSH.

Does this replace Blender's desktop editor?

DeepBlend builds and iterates declared scenes through its supported workbench controls and runtime contract.
It requires a Blender installation. The modeling guide describes the supported generators and edits.

Where do my projects live?

An ordinary installation stores projects below your DSH home. Source-development tools can use a repository-local store.
See storage and recovery before changing that configuration.

Are every platform and every artistic result validated?

The managed Blender download targets macOS arm64; other platforms require their own Blender installation and configuration.
CI also checks selected Linux x64 paths. Actual coverage and open artistic/user-adoption work are recorded in the acceptance register.

Blender's upstream Linux download is linux-x64; Linux arm64 needs a distribution package or a self-built Blender.
The repository's managed installer targets macOS arm64. See the platform details
for executable paths and the limits of cross-platform validation.

For contributors

SceneSpec → Blender runtime → preview / frames → review / delivery. The master specification is SPEC.md.
The host composition owns shared services; the agent preset owns a session's model-visible tools; the runtime executes controlled Blender work.

Development prerequisite	Declared floor
Node.js	≥ 22 for the packages; the DSH CLI needs 22.23.3+

npm run dev:setup
npm run dev:test

Full native acceptance remains a separate entry:

bash deepblend/tests/run-all.sh      # 41 suites; README.zh.md carries the measured snapshot

Development setup · CI scope and artifacts · Architecture decisions

Release and community

Latest release · Changelog · Report a bug · Propose a feature

MIT — License. Security reports follow SECURITY.md. Read CONTRIBUTING.md
for development and evidence requirements. The Chinese README retains the measured test totals and their caveats;
per-milestone conclusions are kept in the acceptance register.