<oembed><type>rich</type><version>1.0</version><title>Dustin wrote</title><author_name>Dustin (npub1mg…gpdjc)</author_name><author_url>https://yabu.me/npub1mgvwnpsqgrem7jfcwm7pdvdfz2h95mm04r23t8pau2uzxwsdnpgs0gpdjc</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>If you didn&#39;t see the full slide deck, the link is here:&#xA;&#xA;https://dtdannen.github.io/Coordinating_(DV)Machines_9JAN2023.pdf&#xA;&#xA;(Warning - it’s a lot of content mashed together)&#xA;&#xA;Generally, you can think of DVMs as being the “actions” or “tools” or “functions” that an agent would call. (These are terms other projects are using; OpenAI refers to them as tools and functions)&#xA;&#xA;Once we have a multi-step DVM chain (like a DVM passes it’s output to another DVM before the final response is given back to the user) then we have an equivalent to a hardcoded LangChain agent. &#xA;&#xA;More flexible agents will choose dynamically which DVMs to use, in which order, to solve problems. That’s where things will get very interesting.</html></oembed>