upvote
Jido originally used Langchain for LLM calls - but it wasn't a fit so I built an entire LLM client package to work with Jido called ReqLLM

https://hex.pm/packages/req_llm

ReqLLM is baked into the heart of Jido now - we don't support anything else

reply
ReqLLM is a key part of my stack, thank you for making it!
reply
Elixir has a LangChain implementation by the same name. And in my opinion as a user of both, the Python version and the Elixir version, the Elixir version is vastly superior and reliable too.

This agentic framework can co-exist with LangChain if that's what you're wondering.

https://github.com/brainlid/langchain

reply
I went down this path a bit the other night, curious what OP's answer is. My mental model was that they could be complimentary? Jido for agent lifecycle, supervision, state management, etc, LangChain for the LLM interactions, prompt chains, RAG, etc. Looks like you could do everything in Jido 2.0, but if you like/are familiar with LangChain it seems like they could work well together.
reply
See my other comment, but Jido 1.0 used (Elixir) Langchain

As LLM API's evolved, I needed more and built ReqLLM which is now embedded deeply into Jido.

reply