Voyager open-sourced vork, a headless 3D and VFX engine where AI agents write entire scenes as code, including custom Slang shaders, and render on the GPU without driving Blender's UI. The 0.5.0 research preview (November 2026, about 1,677 GitHub stars) targets Vulkan and Metal, ships JSON and TypeScript scene SDKs, and documents benchmark comparisons against retained Blender EEVEE timings.
TL;DR #
| Topic | What vork claims |
|---|---|
| API size | Core scene API ~2,500 tokens |
| Agent entry | vork init , README paste prompt,vork skills add |
| Profiles | std/previs ,std/draft ,std/final ,std/path |
| Standout demo | One million birds, 192 frames 1080p, median 96.9 s movie on L4 |
| Cloud | vork cloud on Voyager GPUs when local hardware lacks ray queries |
| License | Source-available free during research preview |
This is not the same product as explainx.ai's October coverage of Voyager as a multi-app creative harness. Vork replaces the GUI with agent-authored scene files.
Why agents need a headless renderer #
Creative agents that only click Blender buttons fight UI latency and non-deterministic layouts. Vork's pitch: agents hold geometry, cameras, lights, and Slang programs in git-friendly text, render, inspect PNG or EXR output, and revise.
That matches RoboWild Fable robot benchmarks in spirit: environments agents can script, but for cinematics and VFX instead of locomotion.
Tesla Digital Optimus demos show gaming-style agent loops going mainstream; vork targets offline renders those agents might generate for marketing or simulation previews.
Architecture under the hood #
Lit sphere with soft green key light for GPU path-tracing setup
Vork is Rust + Slang on Vulkan/Metal:
- Default hybrid path combines raster visibility withhardware ray-traced lighting .
std/pathenables path tracing when interiors go dark under hybrid transport.- Slang hooks let scenes overridecamera rays, materials, light propagation, and film response without forking the engine.
The README is explicit that furnace tests and analytic oracles exist, but no guarantee every scene is physically exact.
Getting started locally #
From GitHub Releases:
vork init my-shot && cd my-shot
vork skills add
vork render scene.json --out render.png
Starter scenes use bundled sphere, box, and grid primitives, so no asset download is required for the first PNG. Use vork init my-shot --language typescript for scene.ts alongside JSON.
Quality tiers are separate from scene content:
| Profile | Use case |
|---|---|
| std/previs | Fast iteration |
| std/draft | 4 samples + OIDN denoise default |
| std/final | 8 samples + OIDN default delivery |
Final can darken glossy interiors; README says try std/path when hybrid fails.
Example shots and credits #
Wireframe cube world model for agent-driven 3D scene authoring
The repo documents real productions with CC0, CC-BY, and Pexels sources:
- Million birds flock from steered Slang compute (crow asset by Alexei Ostapenko, modified).
- Cyber car glTF from Unity Fan adaptation with Poly Haven CC0 environments.
- VFX on footage with Ron Lach Pexels plates and tracked geometry.
- Black hole scene with custom Schwarzschild light propagation hook (numerical, not exact GR).
- Cozy Kitchen adapted from Nicole Morena's Blender splash underCC BY-SA .
Each example lists preparation commands and insists credits travel with renders, a useful norm for agent workflows that remix assets.
Benchmarks vs Blender EEVEE #
Vork's RESULTS.md tables compare complete wall times on NVIDIA L4 against retained EEVEE 5.2.1 measurements, not fresh side-by-side runs on the same day. Important qualifications from the README:
- Vork final uses8 samples + OIDN ; cited EEVEE stills used64 samples without denoise .
- Movie timings include encoding ; EEVEE movie numbersexclude startup after a still prime.
- Path tracing rows show vorkslower than Cycles on carried-forward builds.
Sample 1080p still speedups (vork faster):
| Scene | EEVEE (s) | vork final (s) | Ratio |
|---|---|---|---|
| B-interior.json | 2.892 | 1.738 | 1.66× |
| B-night.json | 2.963 | 1.937 | 1.53× |
| B-blocking movie | 88.072 | 47.082 | 1.87× |
Million birds table lists EEVEE 16-sample projections in the 1,500–2,900 s range versus vork's 96.9 s median movie on skim camera, with heavy caveats that EEVEE numbers are extrapolated, not measured movies.
Builders should rerun benchmarks/run.py on their hardware before quoting ratios in pitches.
vork cloud when local GPUs fail #
README states Vulkan ray queries are required on Linux Windows paths, with Docker runtime for NVIDIA Linux. Apple Silicon needs macOS 15+; Intel Macs are unsupported.
If hardware fails, vork cloud renders on Voyager's cloud GPUs, separate from the open repo license.
Agent skill packaging #
The repo includes skills/vork parallel to products like inference-optimisation-skill. After vork skills add, agents read vork help topic pages instead of guessing JSON fields.
Paste prompt from README:
Run vork init my-shot, read vork help, render a preview and inspect the image. Refine the camera and lighting before rendering at final quality.
Research-preview limits you should read #
Before production bets, read vork help limits:
- Homogeneous fog only; removed
std/fogprograms error even if unused. - Heavy transparency andlarge scenes can fail, especially on Mac.
- Water quickstart is diagnostic; full motion blur is expensive.
- Camera solve / relight examples are estimates, not turnkey pipeline replacements.
Source-available licensing is free during preview; watch NOTICE file for changes.
How vork fits agent creative stacks #
| Layer | Tool examples |
|---|---|
| Harness across apps | Voyager creative agent |
| Native 3D engine | vork (this release) |
| Video models | Amazon Decart acquisition context for generative video elsewhere |
| Robotics sim | LeRobot and GR00T coverage |
Use vork when you need inspectable scene code and deterministic rerenders. Use generative video when you need one-off motion without rigging.
Security and supply-chain notes #
Install only from voyager-so/vork releases. The repo ships SECURITY.md and gitleaks config. Agent-driven installs should pin release hashes, same lesson as Together xorl credential leak.
JSON scene schema in practice #
The README scene.json starter uses version 2 nodes for mesh, light, and camera with std/rounded_box geometry and simple PBR inputs. Agents iterate by changing translation, base_color, and rectangle light energy without opening a viewport.
vork help field PATH is the escape hatch when agents guess wrong field names. That CLI-first docs pattern mirrors Poki's install skill and AWS Quick agent flows: narrow discovery surface, deep help topics.
TypeScript and Python SDKs regenerate JSON; the README stresses existing files are never overwritten on vork init, so agents can safely re-run scaffolding.
Slang programs as the moat #
Generic renders need only JSON. Ambitious shots override light propagation (black hole example) or edge-drawn cyber effects (car turning forest into wireframe). Those hooks are scene-supplied GPU code, not engine forks.
That is closer to how game studios ship HLSL snippets, but sized for agent iteration where the model rewrites Slang between renders.
Blender bridge without living in Blender UI #
integrations/blender includes export paths and benchmark helpers. Cozy Kitchen example imports Nicole Morena's .blend through adaptation layers. You can keep artist-authored assets while agents render headlessly in CI.
For teams still on GUI Blender, use Voyager harness for interactive sessions and vork for batch renders.
Docker runtime on NVIDIA Linux #
README documents Docker runtime when host Vulkan stacks are messy. Pin images the same way you pin vLLM containers in inference skill workflows.
Outputs beyond PNG #
vork help outputs covers control passes and hardware video encoding when available. Agents planning social cuts should read outputs docs before assuming PNG-only.
Denoising and sample budgets #
Default OIDN denoise on draft/final means agents must compare equal sample counts when borrowing EEVEE numbers from README tables. Turning denoise off (--set denoise=false) is supported for A/B fairness.
Interior gloom under std/final is a known failure mode; README tells agents to try std/path instead of blindly raising samples.
Water and FLIP simulation limits #
The Water example uses APIC/FLIP compute in vork's fluid library. README warns it is not a full Houdini replacement: limited spray, authored impulses, no two-way rigid coupling.
Science communicators should not overclaim fluid truth; marketers should show the diagnostic quickstart separately from hero fluid shots.
VFX tracking honesty #
After Rain and seed on footage examples stress tracked cameras and proxy geometry, not inpainting fake worlds. That distinction matters for brand legal: Pexels licence text is quoted per shot.
Robotics and digital twin adjacency #
While vork is offline render, the same agent writes code → GPU sim → inspect frames loop appears in RoboWild and Tesla FSD verification posts. Pipelines that need both robot telemetry video and synthetic overlays may fork: vork for polish, sim harness for physics.
Why stars jumped above 1.6k quickly #
GitHub trending placed vork beside inference-optimisation-skill this week. Both sell agent-native workflows with receipts (benchmark tables, install scripts) instead of announcement-only hype.
Licensing and commercial use #
Source-available during research preview is not MIT. Read NOTICE before shipping client renders. Cloud terms for vork cloud are separate from the GitHub license.
Troubleshooting first week #
| Symptom | README pointer |
|---|---|
| Program compile minutes | First final still after new Slang |
| Mac transparency crash | Reduce resolution; try std/path |
| Fog lookup errors | std/fog removed; use certified fog rules |
| EEVEE compare feels unfair | Match samples and denoise flags |
Community benchmarks you can rerun #
The README ships benchmarks/fetch.py and benchmarks/run.py to reproduce tables on your L4 or A6000. Treat published ratios as hypotheses until your agent logs RESULTS.md locally and you archive the raw JSON beside the MP4.
Related reading #
Sources: vork README (accessed November 22, 2026).