Version 7.1.2¶
Patch release: multi-agent support in the Full Web App generator. Projects with several AgentDiagrams now end up with one generated agent per diagram, and GUI AgentComponents can be bound to different agents individually. Changes span the web modeling editor frontend, the web-app generator, its templates, and the GitHub/Render deploy integration — no metamodel or API-level contract changes.
Highlights¶
All agents are now generated:
WebAppGeneratoraccepts anagent_modelslist (plus a per-agentagent_configsmapping) and emits one subdirectory underagents/<slug>/per agent. The scalaragent_model=/agent_config=parameters are kept as deprecated back-compat shims.Every agent is selectable in the editor: the GUI
AgentComponentproperty panel now lists everyAgentDiagramin the project, not just the one referenced by the active GUI diagram. Previously the dropdown returned a single option and silently collapsed multi-agent projects to one agent.Per-agent WebSocket routing at runtime: the generated React
AgentComponentreads a newVITE_AGENT_URLSJSON map keyed by agent name and opens the WebSocket matching its ownagent-nameprop. The legacy single-URLVITE_AGENT_URLvariable is still emitted as a fallback for back-compat.docker-compose rewrite: one service block per agent with port offsets (
8765+i,5000+i), per-agent volume, and a JSONVITE_AGENT_URLSbuild arg injected into the frontend image.Render deployment rewrite: one
type: webservice block per agent inrender.yamlwith unique per-agent service names (<app>-<slug>-agent-<suffix>).frontend/.env.productionnow carries the same JSON URL map so the React app resolves each component to its own deployed*.onrender.comWebSocket.Name-uniqueness invariant: agent names must now be unique within a project. The frontend hard-blocks rename and add operations that would cause a collision; the generation endpoint returns
HTTP 400with the duplicate list as a safety net. This replaces the previous silent-overwrite behavior where two agents named"Alpha"would clobber each other.