Agent Development Kit (ADK) vs smolagents

Agent Development Kit (ADK) 90

2.13.0 on 2026-10-23 (30). 15 Python releases in the 90 days from 3 August across the 1.x and 2.x lines, from 2.6.2 to 2.13.0, the newest 1.x being 1.39.1 on 2026-08-27 (20). 300 open issues and 261 open pull requests per the 1 October check, and we couldn't see reply times (15). Python is current, @google/adk is at 2.4.0 on npm, the Go module at v1.9.0 (tagged 15 October) and the Java artefact at 1.13.0 (21 October) (15). CI passes per the 1 October check, and 2.7.0 fixed zizmor findings in the workflows (10).

smolagents 34

v1.26.0 on 29 May 2026, 161 days before this check (10). No release in the 90 days to 6 November (0). 416 open issues and 1,045 open issues and pull requests on 6 November, with 144 issues opened in the 90 days to 3 November. Of the 50 newest, 26 had a comment and 1 was closed. Two 2026 CVE records say the vendor didn't respond to the reporter, and seven commits reached main from 8 August to 6 November (6). Python only, and the package is the current one (10). CI with actions pinned to commit SHAs and Dependabot for actions (8). 10+0+6+10+8 = 34.

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.

smolagents 66

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). No telemetry found in the source (25). No human approval hook beyond step callbacks; the local executor restricts imports but the guide says it isn't a security tool, and isolation needs a remote executor (10). The secure execution guide covers LLM-generated code risks, without prompt-injection guidance for tool output (7). OpenTelemetry tracing through OpenInference and run inspection (12). SECURITY.md with private reporting and CVE credit, and the remote-executor RCE was fixed in public, but two 2026 CVE records say the vendor didn't respond (12). 25+10+7+12+12 = 66.

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

smolagents 64

Local-package reading. Official PyPI package with Python 3.10 or newer (20). A public tests workflow runs pytest on Python 3.10 and 3.12 for pushes and pull requests; whether main passes wasn't read (15). 416 open issues and 1,045 open issues and pull requests on 6 November, with 144 issues opened in the 90 days to 3 November. Of the 50 newest, 26 had a comment and 1 was closed. Two 2026 CVE records say the vendor didn't respond to the reporter, and seven commits reached main from 8 August to 6 November (6). Release notes on GitHub tags but no changelog file, and the remote WasmExecutor was removed in a minor release (8). 1.0 since 31 December 2024 (15). 20+15+6+8+15 = 64.

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

smolagents 68

Framework reading. MCPClient loads an MCP server's tools in a few lines (20). max_steps, planning intervals and final_answer_checks bound a run (16). Errors from tools and code go back to the model as observations (14). No built-in retry, idempotency or resume beyond replaying memory (8). Few required parameters and many providers, Python only, and the default model needs a Hugging Face token (10). 20+16+14+8+10 = 68.

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

smolagents 81

Framework reading. A typed Python API with reference pages for agents, models, tools and executors (22). llms.txt and Markdown pages on huggingface.co (10). The docs say when to use CodeAgent or ToolCallingAgent and when a sandbox is needed (17). Tools declare typed inputs in a schema dictionary or from a decorated function (12). Many runnable examples; error classes exist but aren't catalogued (10). Versions tagged with release notes, no changelog file (10). 22+10+17+12+10+10 = 81.