Langchain
The provider-agnostic agent framework, post-1.0: a standard create_agent loop on the LangGraph runtime, middleware hooks, and the largest integration ecosystem.
LangChain 1.0 (October 2025) answered its own bloat discourse by shrinking: the framework now centers on create_agent — a standard tool-calling loop running on the LangGraph runtime — plus middleware hooks and normalized content blocks across providers. Legacy chains moved to langchain-classic. MIT, Python and JS, ~139k stars; LangSmith is the commercial layer.
LangChain spent two years as both the most-used and most-criticized framework in AI — then 1.0 (October 2025) did the unusual thing: it agreed with the critics and shrank. The repo now calls itself "the agent engineering platform," and the framework's center is one well-built thing instead of forty abstractions.
Highlights
create_agent— a standard, production-grade tool-calling agent loop, running on the LangGraph runtime, in one call.- Middleware — hooks at every step of the loop, with built-ins that matter: human-in-the-loop approval, context summarization, PII redaction.
- Normalized content blocks — reasoning traces, citations, and tool calls in one shape across providers; the swap-the-model promise made real.
- In-loop structured output — typed results generated inside the agent loop, not via an extra LLM call.
- The ecosystem moat — the largest integration surface in the category (
langchain-*packages for every model, vector store, and tool), in Python and JS. - A clean escalation path — drop down to LangGraph for custom graphs and durable state; out to LangSmith for tracing and evals.
In an AI-assisted workflow
pip install langchain # or: npm install langchain
# agent = create_agent(model, tools, middleware=[HumanInTheLoop()])The 2026 fit: teams that want a standard agent loop without marrying a provider, and that value the graduated stack (LangChain → LangGraph → LangSmith) over assembling equivalents.
WARNING
The pre-1.0 tutorial corpus is enormous and now misleading — most of it references APIs exiled to langchain-classic. Check dates before following anything, and treat "LangChain is bloated" takes as describing the 0.x era the team itself retired.
Good to know
MIT, ~139k stars, free; the company monetizes LangSmith (freemium per-seat). Where it sits against the data-framework lineage of LlamaIndex — the classic confusion — is exactly the LangChain vs LlamaIndex question; the wider field is Agent Frameworks in 2026.
Frequently asked questions
- Do I still need LangChain in 2026?
- The honest framing the 1.0 release itself embraced: if you're on one provider, a first-party SDK or direct API calls cover simple agents with fewer layers. LangChain's remaining case is real, though — provider-agnosticism (swap models without rewrites), middleware around the agent loop, and the seamless path down to LangGraph for control and out to LangSmith for observability.
- What changed in LangChain 1.0?
- Radical narrowing. The sprawling chain zoo moved out to langchain-classic; what remains is create_agent (a production tool-calling loop built on the LangGraph runtime), middleware at every step, standardized content blocks for reasoning/citations/tool-calls across providers, and structured output generated inside the main loop. Both Python and JS shipped together, with a no-breaking-changes-until-2.0 pledge.
- LangChain vs LangGraph — which do I use?
- They're layers, not rivals: create_agent IS LangGraph underneath. Start with LangChain's high-level API; drop to LangGraph when you need custom graphs, durable state, or long-running orchestration. Same runtime, two altitudes.
Related
- LangChain vs LlamaIndex in 2026: Agents or Data?The classic framework confusion resolved — LangChain's agent loop and ecosystem vs LlamaIndex's data-and-documents depth — and when you'd genuinely use both.
- Which Agent Framework in 2026? LangGraph vs CrewAI vs AutoGen vs OpenAI Agents SDK vs Claude Agent SDKA decision guide to the major AI agent frameworks — control vs. abstraction, multi-agent models, state and durability, and which fits your project.
- LangGraphA low-level library for building stateful, controllable agents as graphs, with checkpointing and human-in-the-loop.
- LangSmithLangChain's platform for tracing, evaluating, and monitoring LLM apps — framework-agnostic.
- LlamaindexThe data framework for LLM apps — ingestion, indexing, query engines, and document agents — now centered on document processing with LlamaParse and LlamaCloud.
- Pydantic AIThe type-safe agent framework from the Pydantic team — validated structured outputs, dependency injection, durable execution, and 'that FastAPI feeling' for agents.
- n8n vs Dify: Which AI Workflow Platform? (2026)Automation-first vs AI-native — n8n's 400+ integrations with agent nodes vs Dify's LLM-app platform with built-in RAG. Licenses, pricing shapes, and the fit test.
- DifyThe visual platform for LLM apps and agentic workflows — canvas-built chatflows, RAG pipeline, agent nodes with 50+ tools, and LLMOps, self-hosted via Docker.
- N8nFair-code workflow automation with native AI — a visual canvas plus code, 400+ integrations, and LangChain-based agent nodes; self-host free or cloud per-execution.