What's the overall flow/architecture/concept of Jido? #43
-
|
I'm relatively new to AI agent frameworks and very new to Elixir, most of my experience has been with Vercel's AI SDK and OpenAI's SDK. I'm trying to create what I think of as an agent, defined as a process or service that can handle a multi-turn conversation, seamlessly call tools and merge tool responses into the stream of user and assistant messages. I've read through the docs but I'm still unclear on how to do this. How do I ask a question and then advance the conversation? What is the data structure for storing the conversation? How do we persist the conversation? How do we load an old conversation and continue it? Etc. I don't mean to presume, but I noticed a Markdown prompt in the repo with instructions for an AI on how to write docs. Am I correct in assuming that the docs are largely AI-written? I think there are some large gaps for newcomers, but that's normal with new projects 🙂 Thanks again for your work on this, I'm new to Elixir and I wasn't sure whether I'd be able to find a framework for writing AI-based apps. Looks like Jido is it, I just need to figure out how it works. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
The docs are 50% AI, 50% human :-) Jido grew out of a Solana bot framework I wrote last year - you are correct it doesn't follow the "OpenAI" way. That was intentional - but the world has moved quickly in the last 6 months and I understand how it can be a bit confusing. I'm working on examples to help with this right now. The quick answer is that you would need to write your own Jido Actions for each of the steps you've mentioned above - storing conversations, etc. Jido then executes these actions like any other function. There's not much yet to support a conversation either - but that's a story for another time. This package may be more useful to you in current form: https://github.com/elepedus/elixir-ai-sdk Jido's getting there and thankfully AI isn't going anywhere! |
Beta Was this translation helpful? Give feedback.
The docs are 50% AI, 50% human :-)
Jido grew out of a Solana bot framework I wrote last year - you are correct it doesn't follow the "OpenAI" way. That was intentional - but the world has moved quickly in the last 6 months and I understand how it can be a bit confusing.
I'm working on examples to help with this right now. The quick answer is that you would need to write your own Jido Actions for each of the steps you've mentioned above - storing conversations, etc. Jido then executes these actions like any other function.
There's not much yet to support a conversation either - but that's a story for another time.
This package may be more useful to you in current form: https://github.com/e…