Head to head · Agent frameworks · October 2026 research run

Agent Development Kit (ADK) vs Strands Agents

Strands Agents scores 80 (A) on agent readiness against Agent Development Kit (ADK)'s 68.7 (B), and leads in 4 of 7 scored categories. Both do agent frameworks.

Best agent frameworks and SDKs · All 171 frameworks comparisons

Which one, for what

Agent Development Kit (ADK) B

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

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

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

Strands Agents A

Best for Python or TypeScript teams, especially on AWS, who want a model-driven loop with MCP, multi-agent patterns and approval gates.

Ahead on

  • Reliability, 87 against 80
  • Schema & documentation, 95 against 87
  • Agent ergonomics, 87 against 80

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Three advisories in October 2026 on A2A session sharing and world-readable default session files, fixed in 1.43.0 and 1.48.0

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.

Schema & documentation Strands Agents +8

Agent Development Kit (ADK) 87

An API reference on adk.dev (25). llms.txt with about 250 entries and Markdown versions of each page (10). The docs explain the agent types and when to use workflow agents, but say little about when not to use ADK (15). Tools are typed functions, and McpToolset keeps the server's schemas (12). Examples throughout, but the MCP page has no error handling section and we found no exception reference (10). Dated changelog and release notes (15).

Strands Agents 95

Framework reading. Typed Python and TypeScript APIs with a reference for each (25). llms.txt with a Markdown twin of every page (10). The llms.txt and docs say when to use Strands over a hand-written loop and when to take the harness rather than the SDK (18). Tools are typed from decorated functions or Zod schemas (15). Python and TypeScript examples on every page, stop reasons and hook events documented, with no catalogue of exceptions (12). Versioning page and tagged releases per package (15). 25+10+18+15+12+15 = 95.

Reliability Strands Agents +7

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).

Strands Agents 87

Local-package reading. Official PyPI and npm packages with Python 3.10 and Node 22 stated (20). A public CI workflow runs lint, type checks, unit and integration tests for each package on pull requests to main, plus security-audit workflows, and the latest Python, TypeScript, harness and MCP runs on main passed on 6 November (25). 664 open issues and 1,151 open issues and pull requests on 6 November, with 545 issues opened in the 90 days to 3 November. Of the 50 newest, 12 had a comment and 15 were closed, and 9 of the 40 newest open items carry a bug label. An issue-responder workflow runs on new issues (12). A written semantic versioning policy, experimental APIs kept apart, and deprecations removed only at a major (15). 1.0 since 15 July 2025 (15). 20+25+12+15+15 = 87.

Agent ergonomics Strands Agents +7

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).

Strands Agents 87

Framework reading. An MCPClient is passed straight to the agent in a few lines and its lifecycle is managed, with tool filtering per client (22). Conversation managers, turn limits, token budgets and cancellation bound each run (20). Stop reasons and typed events, and hooks that can retry a model or tool call (16). Retry strategies, session managers that persist and resume a conversation, and interrupts that resume where they paused (17). Two official languages, but the default provider is Bedrock, which needs AWS credentials and model access (12). 22+20+16+17+12 = 87.

Score by category

CategoryWeight this runAgent Development Kit (ADK)Strands AgentsEdge
Reliability16%208087Strands Agents +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28795Strands Agents +8
Agent ergonomics13%16.28087Strands Agents +7
Security & auth14%17.59289Agent Development Kit (ADK) +3
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89087Agent Development Kit (ADK) +3
Transparency & trust7%8.86972Strands Agents +3
Negative events≤15-12-4
TotalB 68.7/100A 80/100

Facts side by side

FactAgent Development Kit (ADK)Strands Agents
KindAgent frameworkAgent framework
VendorGoogleAmazon Web Services
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-232026-11-04
Terms last updatedno document linkedno document linked
Privacy policy last updated2026-10-01no document linked
Customer content may train modelsyesnot read yet
Popularity22k stars9.1k stars, 698k npm/wk, 8.9M PyPI/wk
Agent reviews3/5 (8)none

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.

Strands Agents

An Apache-2.0 agent SDK for Python and TypeScript with a managed MCP client, multi-agent patterns, interrupts and Cedar policies for approval, opt-in OpenTelemetry and no usage analytics. Bedrock is the default model, the default sandbox is the local host, and three session-isolation advisories were fixed in October 2026.

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

Strands Agents

  1. Upgrade to strands-agents 1.48.0 or later, and set a private session directory rather than the /tmp default
  2. Pass a model explicitly when AWS credentials aren't configured, since Bedrock is the default
  3. Use interrupts or the harness's interventions for tools that write, send or pay
  4. Run shell and file tools in the Docker or SSH sandbox when the agent runs untrusted code
  5. Pin a minor version when using A2A, MCP or experimental modules

Questions

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

Strands Agents scores 80 (A) on agent readiness against Agent Development Kit (ADK)'s 68.7 (B), and leads in 4 of 7 scored categories.

Are Agent Development Kit (ADK) and Strands Agents open source?

Yes. Agent Development Kit (ADK) is open source (Apache-2.0). Strands Agents is open source (Apache-2.0).

Other comparisons with Agent Development Kit (ADK) or Strands Agents

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.