The code layer under most agent tooling — LangChain for chains and tools, LangGraph for stateful multi-step agents.

Pick this when

You're writing the agent in code rather than on a canvas — or you want to know what n8n's AI nodes are actually doing.

What makes it different

n8n's AI features are built on it, per the BC2 trainer — the canvas is a UI over this

LangGraph handles genuinely stateful agents, not just linear chains

The course's advice: point a coding agent at the docs rather than learning it by hand

What it does

Provides the building blocks for agents: models, memory, tools, chains

Runs stateful multi-step agent graphs via LangGraph

What it does not do

Common wrong expectations

Doesn't suit non-technical builders directly — the recommendation is to let a coding agent write against it

Doesn't replace a visual platform for workflows a team has to maintain

Where it sits in a stack

Underneath everything agentic. Worth knowing exists even if you never import it.

Shelf

Dev libraries & frameworks

Our status · not-using

No agent code in the pipeline.

For your projects

Only relevant if the vector phase grows into something agentic rather than a search index.

Freshness

current

Related tools

complementsn8ncomplementsClaude Code

n8n: n8n's AI layer is built on LangChain

claude-code: the recommended way to use it — have the agent write the code

Every moment the course touched it (9)

SessionCoverageMomentWhat happened
Basecamp 2: Vibe Codingexplained0:35:59Code layer under n8n-style tools; agents via LangGraph; non-technical builders should point coding agents at the docs instead of hand-building
Community Session 1: Causa Claims — a Non-Coder's Five-Agent Construction-Claims Pipeline, the Gate as the Product, and What RAG Really CostsexplainedRAG pipeline and agent chaining in Python
Build Reliable AI Apps Using LangGraph: The Travel Agent That Changes Its Mind — State, Nodes, Cycles, Interrupts, and Why the Vocabulary Is the SkillexplainedNamed as the parent company of LangGraph, LangFlow and LangSmith, and disambiguated for the cohort in four lines.
Office Hours III: Backing Up Claude Chats with Obsidian, Bridging Chat and Cowork, What Fable Is For, and the Context-Rot ProblemexplainedFramework under many no-code agent builders
Day 10: Principles for Building Agents — Three Levels of AI, the 7-Question Workflow-vs-Agent Test, Goldilocks Scope, Agent Prompting, and Tool DesignmentionedLocal RAG pairing with Ollama
The Five-Level AI Generalist Roadmap (+ Operating System & Monetization)mentionedL2 orchestration and L4 agent frameworks (with LlamaIndex, CrewAI, AutoGen)
Day 2 (morning): Agentic Workflows in Code - CrewAI from One Agent to a DevOps Crew to a Parallel Investment Adviser with Custom ToolsmentionedAlternative framework
AI Sprint: OpenClaw — Session 1 (Infrastructure, Not Agent: the Seven Documents, 1-Click VPS, and Model Routing)mentionedFramed as an agentic framework — a different layer than a runtime
AI Sprint: AI Evals & Reliability — Day 2 (Testing Systems That Never Answer Twice)mentionedOrchestration references; LangGraph suggested for storing and rating dataset/golden records

← All tools by category