A demo of Vork, a 3D and VFX engine in which coding agents write a scene, render a frame, review the image, and revise it, shows Claude recreating an autumn-tree painting as a 3D simulation.
Vork demo · 3D and VFX engine
An AI agent that renders, reviews and revises its own 3D scene
In a demo of Vork, Claude recreated an autumn-tree painting as a 3D simulation. The agent wrote the scene, rendered a frame, inspected the image and changed the scene based on what it saw.
37 min
Claimed total render time for the painting recreation
1 GPU
A single NVIDIA L4 was used for the render
3 steps
Write, render and review feed a revision loop
The agent loop
Each pass checks the visual output, not just the code
1. Write
Agent writes scene code
→
2. Render
Engine produces a frame
→
3. Review
Agent inspects the image
→
4. Revise
Changes lighting, composition or geometry
Revise feeds back into Write, repeating until the frame matches the target.
Why it matters
Most AI-assisted 3D work generates code or assets without checking the output.
A render-inspect-revise cycle can catch lighting, composition and geometry problems visible only in the image.
The same feedback pattern is spreading to coding agents that read test results or screenshots.
What remains unclear
No independent benchmarks or detailed technical paper were available.
Scene complexity and the amount of human direction are not known.
No quality or cost comparison with traditional rendering pipelines.
Bottom line
One demo illustrates the workflow. It does not prove production readiness.
Holds up?
Needs wider testing beyond a single painting recreation.
Scales?
Render times for more complex scenes remain untested.
Access?
If it works, users could describe a scene and let an agent iterate on modest hardware.
Continue reading The rest of this article is for AI News Blitz readers. Choose an option below to keep reading.
Already purchased? Sign in ✓ Signed in — this article isn’t included in your current plan.Unlocking the full article...