Welcome to llmflows Discussions! #4
Replies: 2 comments 12 replies
-
|
Hello - In my previous company, we implemented something similar as an explicit digraph, with each vertex (flowstep) declaring its inputs and outputs and with edges between vertices. That way we could enforce execution order utilizing a topological sort on the graph itself. I am principal architect at a large company , currently working with LLMs used for complex tasks |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Thank you for the feedback! Great point! Actually, I realized that one should be able to add a whole flow in a functional flow step and make it nested only when I was close to completing the first working version of the framework. So it was definitely not build with this in mind but I am very excited about making this work. Have you tried building a nested flow? Do you have any specific use-cases in mind? |
Beta Was this translation helpful? Give feedback.
-
|
Hi - thanks for the response. Yes, I have used nested 'flows', but not in the context of LLMs. It is all about having reusable processing components in complex software flows. In other words: 'DRY" - Do not repeat yourself. I do have a specific use case in mind that we are specifying, but which is in stealth mode. What I can say is that we are planning to use multiple agents on top of LLMs - so one agent can enlist others to address more complex use cases.. That is where the nesting comes in: it is not always linear. I have shared your doc with the team and will keep you posted. |
Beta Was this translation helpful? Give feedback.
-
|
Great to hear! Any feedback is much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Hello again - for fun, I generated a network graph from your 'critics' example flow and drew it. You may not want to introduce a dependency, but using a graph could simplify your code significantly, and using a topological sort of it would enforce execution order. |
Beta Was this translation helpful? Give feedback.
-
|
@idiotype Hi again! I finally found the time to create a nested flow step example. You can try it out here: If you want to try using nested flows to build a multi-agent system you can potentially draw some inspiration from this blog post I made recently: Instead of a functional flow step that selects a tool, you can have a functional flow step that selects an "agent flow" and each agent flow can have it's own tools etc. To speed things up and run multiple agents in parallel you can also use the AsyncFlow and Async Flowsteps. If you decide to try it out any feedback would be appreciated. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @stoyan-stoyanov - sorry about the delay in responding.; super busy I will try it out soon and review your blog post. |
Beta Was this translation helpful? Give feedback.
-
|
Hey no worries! I am looking forward to your feedback if you end up trying it out |
Beta Was this translation helpful? Give feedback.
-
|
Got distracted - I think you might be interested in this: https://github.com/SqueezeAILab/LLMCompiler/tree/main |
Beta Was this translation helpful? Give feedback.
-
|
Apologies, I somehow missed your message. Thanks for sharing this. I will check it out! |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
To get started, comment below with an introduction of yourself and tell us about what you do with this community.
Beta Was this translation helpful? Give feedback.
All reactions