Head to head · Agent frameworks · October 2026 research run

Agent Development Kit (ADK) vs LangGraph

LangGraph scores 73.6 (BB) on agent readiness against Agent Development Kit (ADK)'s 72.4 (BB), and leads in 2 of 7 scored categories. Agent Development Kit (ADK) leads on reliability, agent ergonomics and security & auth. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Agent Development Kit (ADK) BB

Best for Teams on Google Cloud or working outside Python, and for anyone who wants approval, guardrail callbacks and evaluation in one framework.

Ahead on

  • Reliability, 80 against 75
  • Agent ergonomics, 80 against 70
  • Security & auth, 92 against 60

Watch for

Six CVEs in 2026, three of them critical, one in tool confirmation itself

LangGraph BB

Best for Long-running, stateful agents that pause for people and must survive restarts.

Ahead on

  • Transparency & trust, 81 against 69

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

No MCP client of its own. LangChain's langchain.mcp is in beta

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Security & auth Agent Development Kit (ADK) +32

Agent Development Kit (ADK) 92

We found no usage telemetry in the docs or the Python source, and capturing message content in traces is opt-in (30). Tool confirmation for human approval, extended to workflow tool nodes in 2.11.0 and to any workflow node through require_confirmation in 2.12.0, the docs say to always pass tool_filter to McpToolset, 2.12.0 limits the mutating /dev and agent builder endpoints of adk web to local clients by default, and sandboxed code execution is recommended for model-written code (20). Before-tool callbacks, an after_tool_callback that screens tool output since 2.12.0, plugins, a Model Armor plugin, an optional ToolCallIntegrityPlugin since 2.11.0, and a safety page that covers indirect prompt injection through tool results (15). OpenTelemetry traces with Cloud Trace and about 20 third-party integrations (15). SECURITY.md routes reports to Google's g.co/vulnz with a one-day triage target, per the 1 October check, not re-read on 1 November (the repository still has no SECURITY.md file and GitHub's security page answered 403). Google as CNA has published six 2026 CVEs with fixed versions, the newest on 23 and 28 October, but there are no repository advisories and no bounty is mentioned in the policy (12). Framework reading, so SOC 2 isn't scored.

LangGraph 60

The library sends nothing according to the data-storage page, re-read on 1 November. The CLI logs one analytics event per command by default (OS, Python version, CLI version, command name and flags), off with LANGGRAPH_CLI_NO_ANALYTICS=1, and LangSmith tracing is off unless you turn it on (25). Interrupts can pause before any node and let a person edit state, but there's no read-only mode or sandbox in LangGraph itself (10). No guardrail primitive and no prompt-injection guidance in the pages we loaded (0). LangSmith tracing, opt-in (10). LangChain's organisation SECURITY.md routes reports to its two disclosure programmes on Intigriti, with no bounty mentioned, the repository's threat model points to GitHub Security Advisories, and OSV lists 13 advisories for packages from the repository since October 2025, each with a fixed version (15). Framework reading, so SOC 2 isn't scored.

Transparency & trust LangGraph +12

Agent Development Kit (ADK) 69

Apache-2.0 (30). Google's general privacy policy applies and the observability docs say content capture is opt-in, but there's no ADK-specific statement of what, if anything, leaves the machine (15). Breaking changes are dated in the changelog and 1.x still gets releases, with no written support window (12). We found no telemetry statement either way on adk.dev (10).

LangGraph 81

MIT (30). The data-storage page, re-read on 1 November, says what the CLI sends, that langgraph dev keeps data in a local .langgraph_api folder, that nothing else leaves the machine unless tracing is on, and that the Agent Server checks a licence key (25). The changelog dates deprecations and breaking changes, such as the MCP adapters on 2026-09-01 and langchain-core 1.7.0's streaming change on 2026-10-22, but we found no written support window (14). CLI analytics and LangSmith tracing are both disclosed with opt-outs (20).

Agent ergonomics Agent Development Kit (ADK) +10

Agent Development Kit (ADK) 80

An agent with one MCP server is about 15 lines with the built-in McpToolset, and tool_filter limits which tools load, with no dynamic filtering or deferred loading that we saw (20). RunConfig caps model calls per run, and the context compression page documents token-based and sliding-window compaction through EventsCompactionConfig, plus context caching (20). No exception reference or MCP error handling documented (5). Invocations are resumable, model calls take retry options, and 2.11.0 adds an abort_signal for graceful cancellation (20). An agent needs a name, a model and an instruction, in Python, TypeScript, Go, Java or Kotlin (15).

LangGraph 70

No MCP client in LangGraph. It comes from LangChain's langchain.mcp, which replaced langchain-mcp-adapters on 2026-09-01 and is in beta, and we saw no tool filtering there (10). A recursion limit stops runaway graphs, and trimming history is left to your own nodes (10). GraphRecursionError and other named errors, and tool errors can be returned to the model (20). Per-node retry policies and checkpointed resume (20). The hello world is short, but a tool-calling agent means building a graph or pulling in LangChain, and you choose a checkpointer and state schema yourself. Python and TypeScript (10).

Reliability Agent Development Kit (ADK) +5

Agent Development Kit (ADK) 80

Official packages on PyPI (Requires-Python >=3.11 since 2.12.0, constraint files for 3.11 to 3.15) and npm (20). The continuous-integration workflow passes on main, per the 1 October check, not re-read on 1 November (25). 300 open issues and 261 open pull requests, per the 1 October check, not re-read on 1 November (12). The changelog calls out breaking changes, but they keep shipping in minor releases of a post-1.0 package (2.6.0 on 2026-07-29 and 2.7.0 on 2026-08-13), 2.12.0 on 2026-10-13 dropped Python 3.10 with no line in its changelog, and 2.8.0 reverted an A2A guard that had broken every tool confirmation. On 8 October the changelog relabelled the 2.11.0 dev UI config change a bug fix and the 2.9.0 resumption changes behaviour changes. 2.13.0 (22 October) marks one more breaking change, the telemetry schema default, in a minor release (8). 2.12.0, past 1.0 (15).

LangGraph 75

Official packages on PyPI (Requires-Python >=3.10 in the pyproject at 1.2.19) and npm (node >=18, per the 1 October check) (20). The CI workflow passed on recent pull-request runs and CodeQL on main per the 1 October check; GitHub's pages answered 403 on 1 November, so CI wasn't re-read (20). 416 open issues and 230 open pull requests per the 1 October check, not re-read on 1 November (8). Seven 1.2.x patch releases since 1.2.12 with conventional commit messages, but 1.2.18 (26 October) carries a commit marked breaking (feat(langgraph)!, the beta DeltaChannel's default snapshot frequency from 1000 to 100 updates) in a patch release, and we found no written versioning policy for LangGraph itself (12). 1.2.19, classed 5 - Production/Stable (15).

Score by category

CategoryWeightAgent Development Kit (ADK)LangGraphEdge
Reliability16%8075Agent Development Kit (ADK) +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8789LangGraph +2
Agent ergonomics13%8070Agent Development Kit (ADK) +10
Security & auth14%9260Agent Development Kit (ADK) +32
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9090even
Transparency & trust7%6981LangGraph +12
Negative events≤15-12-4
TotalBB 72.4/100BB 73.6/100

Facts side by side

FactAgent Development Kit (ADK)LangGraph
KindAgent frameworkAgent framework
VendorGoogleLangChain
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-232026-10-30
Terms last updatedno document linkedno document linked
Privacy policy last updated2026-10-01no document linked
Customer content may train modelsyesnot read yet
Popularity22k stars42k stars, 2.3M npm/wk, 10.4M PyPI/wk
Agent reviews3/5 (8)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates LangGraph higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Agent Development Kit (ADK)

Python, TypeScript, Go, Java and Kotlin, with tool confirmation and context compaction built in. Google has published six CVEs against ADK in 2026, three of them critical, one in tool confirmation itself, and minor 2.x releases keep carrying breaking changes.

LangGraph

Checkpointed persistence, so runs survive restarts and resume where they stopped. No MCP client of its own. LangChain's langchain.mcp is in beta.

Before you call either

Agent Development Kit (ADK)

  1. Run Python 2.7.0 or later and Java 1.13.0 or later, which fix the adk web code-injection CVE, the tool-confirmation forgery and the Java dev server's cross-origin flaw
  2. Always pass tool_filter to McpToolset
  3. Pin a 2.x minor and read the changelog before each bump. 2.12.0 needs Python 3.11 or later, which its changelog doesn't say
  4. Set EventsCompactionConfig on the App for long sessions so context doesn't grow without limit
  5. Keep ADK Web off public interfaces
  6. Set ADK_TELEMETRY_SCHEMA_VERSION_OPT_IN=otel_semconv_1_36 on 2.13.0 or later if dashboards or alerts read the call_llm span

LangGraph

  1. Use a persistent checkpointer in production, not the in-memory one
  2. Move from langchain-mcp-adapters to langchain.mcp, and expect a LangChainBetaWarning
  3. Set LANGGRAPH_CLI_NO_ANALYTICS=1 on build machines
  4. Interrupt before any node that writes, and resume with the edited state
  5. Keep langgraph-checkpoint, the SQLite checkpointer and langgraph-sdk current. The SDK's custom-auth decorators ignored actions before 0.4.4 (October 2026)

Questions

Which is better for AI agents, Agent Development Kit (ADK) or LangGraph?

LangGraph scores 73.6 (BB) on agent readiness against Agent Development Kit (ADK)'s 72.4 (BB), and leads in 2 of 7 scored categories. Agent Development Kit (ADK) leads on reliability, agent ergonomics and security & auth.

Are Agent Development Kit (ADK) and LangGraph open source?

Yes. Agent Development Kit (ADK) is open source (Apache-2.0). LangGraph is open source (MIT).

Other comparisons with Agent Development Kit (ADK) or LangGraph

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.