vork Puts a 3D and VFX Engine in the Hands of AI Agents
voyager-so's source-available renderer gives agents a small API, a help system and a render-inspect-revise loop instead of an editor.
A renderer that assumes the author is a program
voyager-so/vork, described by its authors as a headless 3D and VFX engine for AI agents, is in research preview. Created on 2026-11-05, it had 1,529 stars and 129 forks by 2026-11-14, per the project's GitHub page, meaning eight days of growth for a vork 3D engine built for agents rather than people. It is written in Rust and Slang, tags itself with ray tracing, GPU, Metal and rendering topics, and is source-available and free during the preview.
No editor: the agent writes, renders, looks, revises
The premise is that most creative tools expose controls a person operates, while an agent can write a shader in the middle of a shot. vork hands the agent geometry, ray queries and GPU execution, then lets scene programs define materials, cameras, light propagation, simulation and compositing. The core API fits in about 2,500 tokens, which matters when it has to sit inside a model's context.
The loop the announcement describes: an agent writes a scene, renders it, inspects the image and changes the code. There is no editor to drive. Ordinary shots need only scene data; the programming hooks are there for shots that need something unusual.
Getting started is short. vork init my-shot scaffolds a project, vork render scene.json --out render.png produces an image, and vork help supplies concepts plus field-level references. The starter uses only bundled sphere, box and grid primitives, needs no downloads, and can be initialised without a GPU. A --language typescript or --language python flag generates an editable scene.ts or scene.py beside the ready-to-render JSON. Render profiles separate scene content from quality: std/previs for iteration, std/draft at four samples, std/final as the delivery default and std/path for path transport, with OIDN denoising on by default for draft and final.
Rendering needs Apple Silicon or an NVIDIA GPU with Vulkan ray queries. Authoring and vork help work without one, and Voyager offers vork cloud for rendering on its own GPUs.
The speed numbers arrive with their own rebuttal
The demo: one million simulated birds steered by Slang compute programs, 192 frames at 1080p in 97 seconds on a single NVIDIA L4, against a 13 to 18 minute projection for Blender EEVEE at the same sample count. Across default stills and movies the project measures 1.1 to 2.3 times faster than EEVEE, and roughly 8 to 11 times on the bird flock.
The announcement then argues against reading those as like-for-like wins. The timings are explicitly not equal-quality speedups: vork final used eight samples with OIDN where EEVEE used 64 without denoising, and visual review found softer edges, grainier defocus, wall mottling and changed sparse or spectral highlights at those budgets. Nineteen earlier quality comparisons failed their declared no-worse FLIP condition and were not repeated for this build. The Blender 5.2.1 figures were carried over rather than re-run, EEVEE movie times exclude startup and loading, and a million-stars stress scene ran out of GPU memory in both profiles. Read the numbers as direction, not parity.
Limits and open questions
Pricing after the preview is not stated. The source says source-available but gives no licence terms, so what a builder may ship is unclear from this text. vork cloud availability and cost are not described. The comparisons come from a single GPU model.
What it means for people building with AI
The interesting part isn't the birds. It is the interface shape: a compact API, a help system the agent can query, and a render-inspect-revise loop rather than a GUI. That pattern transfers to almost any heavy tool you wire an agent into, and the same discipline of small surface area and self-checking output applies when writing effective prompts. Draftship's AI app builder turns a plain-language description into a hosted app with a database and sign-in, a different layer of the stack; nothing here indicates Draftship supports vork or the reverse.
Primary sources
- voyager-so/vork: Headless 3D and VFX engine for agents. Research preview. · GitHub trending AI repositories, Nov 14, 2026
This article was drafted with AI assistance from the primary sources listed below and checked automatically against them. An editor hasn't reviewed it yet.