LangGraph vs Exa
Side-by-side trajectory, velocity, and editorial themes.
LangGraph's 1.2.x line is in stabilization mode after the v3 streaming push
Recent releases are patch-level: checkpoint and delta-channel correctness fixes, updateState edge cases, and dependency bumps, plus two small CLI features. The heavier capability work — v3 streaming on RemoteGraph, named tool-dispatched subagents — landed in 1.2.3 and is now being hardened rather than extended.
The team is paying down correctness debt around the delta-channel/checkpoint machinery that underpins durable, resumable agent state, and keeping the CLI in step. This is the consolidation phase of a feature cycle: fewer new surfaces, more reliability on the ones just shipped.
Expect continued 1.2.x patches closing checkpoint/streaming edge cases before the next minor introduces new agent-runtime capability; the CLI will keep gaining deployment ergonomics like the HTTPS and API-version-range options just added.
Exa is pushing past search into autonomous web-research agents.
Exa has moved beyond its search-and-retrieval API into agentic territory. The headline change is Exa Agent — a research agent built on Exa's index and reachable via API — now joined by MCP availability for Agent and Connect. The underlying search product keeps maturing in parallel: auto-routing, people and company search, markdown-native content, and instant results.
The arc runs from primitives to products: a fast index, then specialized verticals (people, companies), now an agent that composes them into end-to-end research. Bringing Agent and Connect to MCP signals Exa wants to be a retrieval backend inside other agent stacks, not just a standalone API.
Expect Exa to deepen the agent layer — structured research outputs and monitoring already appear in the changelog — and to lean on MCP distribution to embed inside third-party agents rather than compete for end users directly.
See more alternatives to LangGraph →
See more alternatives to Exa →