https://tube.tchncs.de/videos/watch/85c2899b-f811-43bb-95c1-dd6b8a5482df 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 widget. Strings become text inputs. Booleans become checkboxes. Lists get add/remove controls. Nested mappings become fieldsets. 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, unexpected properties -- all flagged immediately. This makes complex configuration accessible to people who would never write YAML by hand. Wed, 10 Jun 2026 02:53:57 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://video.dresden.network https://video.dresden.network/lazy-static/avatars/13138cac-4ad8-4520-bf15-e94c7f8b57bf.png https://tube.tchncs.de/videos/watch/85c2899b-f811-43bb-95c1-dd6b8a5482df All rights reserved, unless otherwise specified in the terms specified at https://video.dresden.network/about and potential licenses granted by each content's rightholder.