Agent Graph
The Agent Graph visualizes the configuration connected to one root agent. It can also include that root agent’s sub-agents and skills.
Beta editor: The graph and side-panel editor are still limited. Use Edit to open the full Node-RED flow editor for authoritative configuration and wiring.
Selecting An Agent
Section titled “Selecting An Agent”Only root agents appear in the graph selector. A +N indicator shows how many
sub-agents are associated with a root agent.
Selecting a root agent loads its configuration graph, including related sub-agent nodes returned by the runtime.
| Card | Meaning |
|---|---|
| Agent | The root or sub-agent agent node. |
| Behaviour | Instructions, planning, iterations, router, and debug configuration. |
| Model | Reusable model configuration. |
| Connection | Model-provider connection. |
| Memory | Facts and event storage configuration. |
| Budget | Optional usage limit. |
| Skills | Studio-created grouping for selected skills. |
| Skill | An agent-skill node and its actions. |
The Skills card is a visual group, not a Node-RED node. agent-in, standard
Node-RED nodes, and the implementation flow behind each skill are not shown.
The Skill side panel can edit some fields on existing actions and parameters, but it does not currently add or remove them or manage Node-RED output ports and wiring. Type and Target are not constrained to supported values in the Studio form. Maintain and verify skill definitions in Node-RED.
Legacy Inject nodes selected through the Agent node’s compatibility path are not represented as Skill cards.
The beta graph may not display every deployed Model field consistently. Verify
the active Model ID and generation settings on the Node-RED agent-model
configuration node when the Studio card is incomplete or uses different
labels.
Shared config nodes may appear connected to more than one agent. Editing a shared node can affect every agent that references it.
Inspecting A Card
Section titled “Inspecting A Card”Select a card to open the side panel. The available fields depend on the node type. Some IDs and store selectors are read-only.
Studio’s editor does not yet expose every current Node-RED field. In particular, reasoning, planning, model-role, credential, and some advanced fields may need the full editor.
Do not infer that a field is unsupported just because it is absent from the Studio side panel.
Graph Controls
Section titled “Graph Controls”The graph provides pan/select modes, zoom controls, optional minimap, background styles, and local layout interaction.
Visual dragging or edge manipulation in the graph should not be treated as deployed Node-RED wiring. Use the full editor to confirm and deploy actual flow connections.
Configuration Source Of Truth
Section titled “Configuration Source Of Truth”When Studio and Node-RED show different labels or values:
- Open Edit.
- Inspect the deployed Node-RED node and its config nodes.
- Use the node reference in these docs to interpret the current runtime.