
Sign up to save your podcasts
Or


This is a killer feature. Some configuration fields require structured data as YAML.
Let's look into the example of building tools. They can be used by AI Agents, MCP, and others.
The downside: you have to provide the input arguments in a specific form so that we can upcast the data before calling the tool.
Most users won't ever do that, and it's error prone.
Now: the config schema defines the structure, and the modeler turns that into a frontend
You can toggle between the structured editor and raw YAML at any time. Changes sync both ways.
And in YAML mode, you get real-time schema validation. Type mismatches, missing required fields,
This makes complex configuration accessible to people who would never write YAML by hand.
By This is a killer feature. Some configuration fields require structured data as YAML.
Let's look into the example of building tools. They can be used by AI Agents, MCP, and others.
The downside: you have to provide the input arguments in a specific form so that we can upcast the data before calling the tool.
Most users won't ever do that, and it's error prone.
Now: the config schema defines the structure, and the modeler turns that into a frontend
You can toggle between the structured editor and raw YAML at any time. Changes sync both ways.
And in YAML mode, you get real-time schema validation. Type mismatches, missing required fields,
This makes complex configuration accessible to people who would never write YAML by hand.