for agents/llms.txtv0.14.203

Home / Articles / LangGraph and us: how the way we build agent pipelines maps to LangChain, LangGraph, LangSmith and the agent testing toolkits, what is the same, what we do differently, code for each function and every step saved to a vault, what we can learn from them, and where they could run inside our own pipelines

LangGraph and us: how the way we build agent pipelines maps to LangChain, LangGraph, LangSmith and the agent testing toolkits, what is the same, what we do differently, code for each function and every step saved to a vault, what we can learn from them, and where they could run inside our own pipelines

By · 2026-11-21 · article v1.0.0 · newsroom v0.14.192 · langgraphlangchainevalsagentsdeterminismvaultsarticle

Abstract: A lot of what we do maps to LangGraph and LangChain, and I wanted to see how much. LangGraph's state is our vault; its nodes are our agents and our plain code; its checkpoints and time travel are sgit's history; its interrupts are our protected environments and reviewers' verdicts; its middleware is our behaviour policies; LangSmith's traces and evaluations are our signed commits, call ledgers and evals. The ideas are the same. The default is different. We write specific code for specific functions, load, extract, transform and save, and use a model only where judgement is needed; we store everything at every stage, raw and curated, in vaults others can read; and we score in code wherever we can. That gives us more determinism, more control and less black magic, and it is what let the PHP desk, PrompTugal and the Swarm scale. But they have learnt things we should take: one readable definition of the graph, interrupts as a first-class part of the runtime, versioned datasets pinned in CI, and a common trace format. And where a tool is good, we should use it inside our pipeline: Inspect and promptfoo for evals and red teaming, OpenTelemetry for traces, and LangGraph itself where a customer already runs it, with its checkpoints saved to a vault.

LangGraph's concepts and ours: the same ideas, with a different default.

In short

The landscape today

LangGraph describes itself as a "low-level orchestration framework for building stateful agents" (its repository); it reached 1.0 in October 2025 and is at 1.2.24 today, under the MIT licence. LangChain, also MIT and now at 1.5, builds agents on top of it with create_agent, whose middleware hooks are, in its own words, the defining feature (LangChain v1). LangSmith adds tracing, datasets and evaluations, from a free developer plan to 39 dollars a seat a month (pricing), and hosts graphs as LangSmith Deployment. Around them: the OpenAI Agents SDK, CrewAI, Google's ADK, Pydantic AI, the Claude Agent SDK, and Microsoft's Agent Framework, which reached 1.0 in April and replaces AutoGen and Semantic Kernel (Visual Studio Magazine).

How we map

Where we differ

The ideas are the same. What differs is the default, and that is where most of our determinism comes from.

That is what let these pipelines scale from one article to the PHP story, to PrompTugal's 73 articles in ten days, to the Swarm. Less black magic: when something is wrong, the step, its input and its author are all on file.

None of this is impossible in LangGraph, which is low-level and can be as deterministic as you make it. The difference is the habit, not the library.

What we can learn from them

Should we use them?

Yes, inside our pipeline, where each is good, and with its results saved to a vault like everything else:

What I would not do is put a framework at the centre and our pipeline around it. The centre is the data and its history; frameworks are tools that read and write it.

The criticism, fairly

LangChain was criticised early for abstractions on abstractions that made simple things complex and debugging hard (Max Woolf, 2023; Octomind, 2024), and Anthropic's own guidance is to start with direct calls to the model (building effective agents). Most of that criticism predates version 1, which promised no breaking changes until 2.0 and made the agent loop explicit with middleware (releases). LangChain's own answer is that LangGraph has no hidden prompts (how to think about agent frameworks). Both are fair. It is also why we use them as tools, not foundations.

What this does not claim

Where this comes from

My own thinking in writer-10's session on 21 November 2026; the projects' own documentation, repositories and package records, read that day and linked above; and our earlier articles on how our pipelines work. Related: almost working, capture first, one vault, ten agents, the swarm, one real run at a time, one night on Mistral, feature behaviour policies.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 522 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.