What a tron is
A tron is one machine made of several models. It has agents, wiring between them, memory, and a place to put files, and it is the unit everything else in Vibetron is scoped to.
One machine, not one model
Every page in the app lives under a tron, and its URL carries the tron id, which is why a link to a canvas or a conversation is shareable and a reload lands where you were.
Agents, memory and wires
An agent is one model with a soul, its tools and its limits (see Agents). A memory node is a store the tron keeps, of one of five kinds (see Memory). A wire means one of three things: action (the agent delegates a task to another and waits for the answer), message (it sends and does not wait), or memory (a store feeding an agent, read only or read and write).
What belongs to a tron
The canvas drawing and its agents, the memories, the workspace, the schedules, the bridges, the API keys, the libraries its agents are given, and three settings of its own: startup commands, Python packages and Keep attachments. A tron belongs to a person or to a company, and every cap it meets is its owner's.
Startup commands
Garage → Startup. Shell commands the container runs with bash at every start, before the agents, as the container's user and never as root, for at most 60 seconds. A failure or the time limit does not stop the tron: the runtime starts anyway, and the output is in the log.
Python packages
Garage → Startup. The tron's requirements.txt: one package per line, versions pinned (numpy==2.2.6). The container's root is read-only, so pip in a startup command does not work; this field does. The deploy installs the packages once per list and image and puts them on the path of every agent and script. A pip error stops the deploy (409 python_requirements_failed, with pip's last lines) and leaves the tron as it was.
Creating one, and importing one
Three ways in, each making a new tron in your account: an empty one (POST /trons), one from a .tron document or a .tron.zip (POST /trons/import, see The .tron document), and one installed from the published catalogue (POST /published-trons/:id/install), which imports the published document as a copy of your own.