Voro Lab is the part of Voro a coding agent works in. It ships in the lab/ folder of your download. The agent writes graphs and modules as ordinary files, runs them on your GPU and renders pictures to check its work. You then open the result in TouchDesigner. The Lab needs nothing else installed: it uses the Python that comes with Voro.

What the agent makes

Voro runs a graph of modules: shapes, simulations, materials, a camera, a renderer. A graph is a .voro file that connects modules and keeps their settings. A module has named inputs, outputs and controls, and its source sits in its own folder.

Most ideas need only a graph of the modules Voro already has. The agent writes a new module only when the idea needs behaviour that does not exist yet, such as a new image effect, a simulation step, a material or a touch surface.

Start it

1. Make a folder for the work, outside the Voro folder.
2. Give your agent lab/START_HERE.md, your idea and that folder.

That page tells the agent everything else: the commands, which guide to open for which kind of work, and how to check a result by looking at it. The Lab’s guides, skills and examples are all in lab/. The agent reads only the ones the idea needs.

While it works, the agent can keep a graph running and render a new picture every time it saves an edit. Ask it for stills or a short recording when you want to see where it is.

Bring it into TouchDesigner

The agent leaves you a folder holding the graph and its modules. Ask it for a short note naming the controls worth touching.

To open the graph, place voro_import_graph, set Graph File to the .voro file and press Import. The graph arrives as one COMP of ordinary Voro operators that you can open and edit. The COMP’s output shows the graph’s picture. If the agent chose controls to expose, they appear as parameters on the COMP.

To place a single module on its own, use voro_load_module: set Folder to the module’s folder and press Load.

Keep the graph and its module folders together. The graph finds its sources relative to its own file, so you can move the whole folder.

When something fails

Ask the agent to keep the exact error message and the output of the Lab’s env command. That command shows which Voro install the Lab is using. Send those with your report, as described in Reporting a problem. Reports can contain local paths and your own work, so read them before you send them.

The Lab’s commands and flags may change between versions. Graph files, modules and their names are the parts that stay.