Agents in parallel
Several agents can work on the same project at the same time. This page explains how to follow them and what stops them getting in each other’s way.
Two ways to run several agents
Section titled “Two ways to run several agents”- Several conversations: send a request in each one. A conversation handles one request at a time.
- The orchestrator: the independent missions of a single step start together, one per specialist.
There is no limit on the number. More agents go faster, but they also use up the quota of your subscriptions faster.
Following their work
Section titled “Following their work”- Vue d’ensemble (Overview) (
Ctrl+2) shows each conversation in a window, with its own message box. Under Disposition (Layout), choose Auto, 1 to 4 columns or Focus. Drag a window’s title to move it, its edges to resize it. Double-click the title to enlarge it. - The Activité (Activity) panel lists the agents at work. Click one to see its status and actions.
- The status bar, at the bottom of the app, shows for example “4 agents en cours” (4 agents running).
To stop:
- a conversation: the square in its window, or Arrêter cette conversation (Stop this conversation) on right-click. The others carry on;
- a single agent: Arrêter cet agent (Stop this agent), in the Activité panel;
- the whole project: Arrêter tous les agents (Stop all agents), in Vue d’ensemble.
What Island Pilot protects
Section titled “What Island Pilot protects”The UEFN editor and Blender receive commands one at a time.
| What is touched | What happens |
|---|---|
| An island asset or actor, a Verse file, the Blender scene | The first agent to modify it reserves it until the end of its mission. Another agent waits up to 45 seconds, then moves on to something else without changing anything |
| A Verse compilation, a game session command | It waits until the other agents finish their step in the editor, for up to 10 minutes, then goes ahead on its own |
| Any other project file | No reservation. A file changed since it was read is refused: the agent re-reads it and proposes its change again |
While an agent waits, the Activité panel says so, for example “En attente : Verse Coder a réservé le fichier Verse boutique.verse pour sa mission en cours.” (Waiting: Verse Coder has reserved the Verse file boutique.verse for its current mission.) An orchestrator and its specialists share their reservations. After a compilation, the agent is told what the others were modifying, so that it does not correct their work for them.
See also Several agents in the editor.
What is not protected
Section titled “What is not protected”- Your own changes: if you change something by hand while an agent is working, nothing warns it. Avoid changing what it is working on.
- The consistency of the game: a reservation prevents two writes in the same place, not two incompatible decisions. Give each agent a clearly separate task.
What waits for the work to finish
Section titled “What waits for the work to finish”The project is not reconfigured while an agent is working on it: profiles, connections and Changer de moteur (Switch engine) answer “Arrêtez les agents de ce projet avant de le modifier.” (Stop the agents in this project before changing it.) A gateway can only be changed if no agent is working, across all projects.
An action with an unknown result blocks changes to the whole project until it has been inspected, for all agents.