Description
Agent Composer uses a YAML-based configuration format to define workflow graphs. This page describes the root-level fields and basic node structure.Root-Level Fields
At the root level, the Agent Composer YAML format accepts four main fields:inputs
Lists the inputs of the graph mapped to their accepted types. Type annotations should conform to Python typing syntax.
The main graph currently only accepts a single
str input named query, unless used as a subgraph.outputs
Lists the outputs of the graph mapped to their types. A graph can have arbitrarily many outputs, as long as their types are JSON-serializable.
nodes
Lists the nodes in the graph and specifies how they are connected.
ui_output
Specifies exactly one of the fields listed under outputs as the UI output. Required when there are multiple outputs; optional for single-output graphs.
Node Format
Nodes represent basic operations in the graph. A typical node definition:Core Node Arguments
| Field | Description |
|---|---|
type | The step type (must be registered in the component registry) |
config | Configuration arguments passed to the step constructor |
input_mapping | Describes how nodes connect to each other |
config_overrides | Dynamic configuration determined at runtime |
ui_stream_types | Controls what data streams to the UI |
Config Parameters
Config parameters are passed as keyword arguments to the step constructor. Nested configurations are supported:If a config field is not specified, the platform agent configuration setting is used as the default.
Input and Output Nodes
Every graph has an implicit input node named__inputs__. Access inputs via: