Langchain is a publication focusing on programming languages, language design, and compiler development. Readers can explore articles covering topics such as language features, syntax design, and compiler optimization techniques. Additionally, they can learn about programming language theory, language implementation challenges, and practical applications of language design principles.

LangChain

LangChain's CEO explains why they haven't built a visual workflow builder despite frequent requests. The argument centers on workflow builders being squeezed from two directions: simple use cases are better served by no-code agents (prompt + tools), while complex scenarios require code-based workflows like LangGraph. As AI models improve, the middle ground for visual workflow builders shrinks—agents handle more complexity reliably, and code generation lowers the barrier for building sophisticated workflows. The focus should shift to making no-code agents more reliable and improving code generation for LLM-powered systems.

Not Another Workflow Builder

<p>Workflow based solutions also have some inherent benefits though.</p>
<ol>
<li>You can store the results for each step and continue from there. In a full code environment you always have to run the entire code again or you have to implement some kind of step caching manually. This is especially helpful when creating the thing, especially if you have very large datasets you let ai analyze or if you have more than a few llm requests.</li>
<li>It is way easier to have reliability baked in into a step by step process instead of allowing an agent to do anything it wants while giving it tools. This might be magical, but its less reliable.</li>
<li>Often customers have specific needs “When i get email x, i want it to be summarized and be sent to y, then i want a response automatically written, which needs be approved by z”. If you have a strict workflow for this, you can rest in knowing exactly this will happen. If you have some automated agents in the background doing whatever, i think then you have a problem.</li>
</ol>
<p>Your mentioned tools are great too and have their place, but saying that they are inherently better in all of their ways compared to workflow ui based solutions is wrong.</p>
