3 ms·
We're moving our entire codebase away from Langchain and related products (langgraph, langsmith). I originally thought the library had potential and just needed
by Ldorigo 2y ago
We're moving our entire codebase away from Langchain and related products (langgraph, langsmith). I originally thought the library had potential and just needed some polishing which would come with time, but it's just been getting worse and worse. LCEL is the weirdest half-baked idea; it's a nice gimmick that makes your code impossible to debug in a step through debugger. Random stuff breaks with every other release. I deeply regret using it by now.
- maeil 2y agoAre you replacing LangGraph with something else? I've luckily avoided LangChain exactly because it's a black box, but been on the lookout for some kind of DAG visualization of LLM flows. LangGraph pops up first on any related searches.
- jackmpcollins 2y agoI haven't used LangGraph myself, but the latest magentic release is compatible with it if you'd like to check out the examples here https://github.com/jackmpcollins/magentic/issues/287 https://github.com/jackmpcollins/magentic/issues/287
- Ldorigo 2y agoWe're not sure what to do with langgraph yet, interested if anyone here has tried viable alternatives. We could implement a simplified execution graph in-house, but it feels like reinventing the wheel. Also thinking to keep the "graph" part of langgraph but replace all everything else (i.e. tool calls, retrievers, etc.) by non-langchain alternatives.