Head to head · Agent frameworks · October 2026 research run

AgentOS vs smolagents

AgentOS scores 75.8 (BB) on agent readiness against smolagents's 58.7 (C), and leads in 6 of 7 scored categories. Both do agent frameworks.

Best agent frameworks and SDKs · All 171 frameworks comparisons

Which one, for what

AgentOS BB

Best for TypeScript teams that want long-term memory, personas, voice and channel adapters and multi-agent teams in one package, and that will pin versions.

Ahead on

  • Reliability, 77 against 64
  • Schema & documentation, 92 against 81
  • Agent ergonomics, 74 against 68
  • Security & auth, 81 against 66
  • Maintenance & community, 87 against 34
  • Transparency & trust, 70 against 65

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card

Watch for

Version 0.15.69, with 95 release tags after 0.14.2 to 1 November 2026 and breaking minors 0.14.0 and 0.15.0 in that time

smolagents C

Best for Small Python projects and research that want code-writing agents with minimal abstraction.

Also in its favour

  • No key needed to call it

Watch for

No release since 1.26.0 on 29 May 2026, and few commits to main since August

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.

Maintenance & community AgentOS +53

AgentOS 87

0.15.69 tagged on 2026-10-31 (30). 333 release tags in the 90 days to 1 November and 95 after 0.14.2, read from the repository because npm didn't resolve from the shell (20). Little outside traffic to judge by. Of 244 commits since 17 October, all but four are by the maintainer. Per the 8 October check, not re-read on 1 November, two outside issues were closed with five comments each and one outside suggestion had been open without a reply since 12 September (15). The npm package is current by its tags, though the registry couldn't be read on 1 November (15). CI and coverage run on every push, but the workflows have no npm audit step and the repository has no Dependabot configuration file. The security page says Dependabot alerts are on in the repository settings, which we can't see (7).

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.

Security & auth AgentOS +15

AgentOS 81

No analytics or telemetry code found in the source, and the privacy and security pages say the runtime sends nothing to the vendor. OpenTelemetry is off by default and the host installs the exporter (30). Approval gates on five triggers, five security tiers and a rule that composed tools chain a side-effecting step only when the host lists it. Agent-written code runs by default in an in-process node:vm context with a 5-second limit and no memory cap, off unless the host enables it. An optional QuickJS executor runs each call in its own WebAssembly instance with a memory cap. No gate is on unless configured (17). SECURITY.md names model output, tool results and retrieved content as untrusted input, and injection detection is an opt-in extension pack. The security page says that pack's default ONNX model has no prompt-injection label, so injection is scored only when that model can't load, and points to a phrase-list guard (11). OpenTelemetry spans, a usage ledger, a reasoning trace and an opt-in signed audit log (15). SECURITY.md with a private advisory form, acknowledgement in 5 business days and disclosure at 90 days, and the site's security page now gives the same times. No security.txt, no bounty and no published advisory found (8). Framework reading.

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.

Reliability AgentOS +13

AgentOS 77

Official npm package with Node 22 or newer stated in package.json on 1 November (20). A public CI workflow builds, lints, type-checks and runs the tests with coverage, and the 12 most recent runs on master on 8 October 2026 passed, per the 8 October check, not re-read on 1 November (25). 16 open issues and pull requests in total, most filed by the maintainer, with one outside suggestion from 12 September unanswered, per the 8 October check, not re-read on 1 November (20). Written release rules give a breaking change a minor version, and a workflow fails a pull request with a breaking-change marker unless a maintainer approves it, but feature commits ship as patches and breaking minors 0.11.0 and 0.12.0 (7 October), 0.13.0 (8 October), 0.14.0 (17 October) and 0.15.0 (21 October, two persona changes marked BREAKING CHANGE) landed within two weeks (12). Version 0.15.69, not declared stable (0). Local-software reading.

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.

Schema & documentation AgentOS +11

AgentOS 92

Typed TypeScript API with a TypeDoc reference (25). llms.txt on agentos.sh and docs.agentos.sh (10). The guides say which surface to reach for, for example agency-level approval for most apps and workflow nodes for an explicit graph, and the tool-forging docs state what each executor does not isolate (16). Tools take Zod schemas (15). 22 runnable examples and a cookbook, with CLI error codes documented but no single page for the library's error classes found (11). Release notes are generated for every release and published as GitHub releases under written version rules. The CHANGELOG.md on master still stops at 0.13.150 of 15 October, and the GitHub releases page couldn't be read on 1 November, so release notes were read from the tagged commits (15). Framework reading.

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.

Agent ergonomics AgentOS +6

AgentOS 74

An agent is about five lines with the provider detected from the environment, and capability discovery selects tools by meaning, but no MCP client was found in the package source on 1 November or in the docs sitemap, which this line is read on for a framework (12). Session history is capped at about 120K tokens by default, with history.maxTokens, reseed() and maxSteps (20). Typed error classes and a fallbacksUsed field on results, with error documentation spread across pages (14). Checkpoints replay or re-run a node by its declared effect class on resume, and providers fall back in order, though the shipped checkpoint store is in memory (18). Few required options, TypeScript only (10).

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.

Transparency & trust AgentOS +5

AgentOS 70

Apache 2.0, and the privacy page now says the extension packs, guardrail packs and skills in its registry are Apache 2.0 too (30). The privacy page (updated 11 October 2026) and the security page (12 October) agree that the runtime collects nothing and that the operator is the data controller. Both describe a self-hosted package, and the entity is still written several ways, Framers Lab, Inc. in llms.txt, Frame.dev on the legal pages and Framers in the licence (22). SECURITY.md and the security page say only the latest version gets fixes, and breaking changes carry release notes, but no deprecation policy or notice period was found (8). No telemetry is sent and the site says so (20).

smolagents 65

Apache-2.0 (30). The library stores nothing itself; the default model sends prompts to Hugging Face's inference providers, which the docs show (20). Breaking removals such as WasmExecutor shipped in minor releases, without a written deprecation policy (5). No telemetry, though no page states it (12). 30+20+5+12 = 67.

Score by category

CategoryWeight this runAgentOSsmolagentsEdge
Reliability16%207764AgentOS +13
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29281AgentOS +11
Agent ergonomics13%16.27468AgentOS +6
Security & auth14%17.58166AgentOS +15
Payments & pricing10%12.56060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88734AgentOS +53
Transparency & trust7%8.87065AgentOS +5
Negative events≤15-2-6
TotalBB 75.8/100C 58.7/100

Facts side by side

FactAgentOSsmolagents
KindAgent frameworkAgent framework
VendorFramers Lab, Inc.Hugging Face
Hosted endpointno (local only)no (local only)
Transports
AuthAPI keyNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-312026-05-29
Terms last updated2025-11-062022-09-15
Privacy policy last updated2025-11-062023-03-28
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity677 stars, 5.3k npm/wk30k stars, 171k PyPI/wk
Agent reviews2.8/5 (4)none

How the scores have moved

AgentOS

smolagents

No score change since it was listed.

Verdicts

AgentOS

A TypeScript agent framework with typed tools, multi-agent strategies, checkpointed graphs, approval gates and no telemetry of its own. It is at 0.15.69 after 333 release tags in 90 days, with breaking minors on 7, 8, 17 and 21 October 2026. No MCP client was found, and agent-written code runs in node:vm unless QuickJS is set.

smolagents

A compact Python library for code-writing and tool-calling agents, with MCP tools, any model provider and remote sandboxes through E2B, Docker, Modal or Blaxel. The newest release is 1.26.0 of 29 May 2026, a critical remote-executor RCE took about eight weeks to fix, and the local executor isn't a security boundary.

Before you call either

AgentOS

  1. Pin an exact version of @framers/agentos. Feature commits ship as patch releases while it is 0.x, and breaking changes ship as minors
  2. Leave emergentConfig.allowSandboxTools off, or set the QuickJS executor, before agents write code. The default node:vm executor shares the host process
  3. Pass your own ICheckpointStore to compile() for runs that must survive a restart. The default store is in memory
  4. Set hitl.approvals.beforeTool for tools that write, and choose a handler. No approval gate is on by default
  5. Use Node 22 or newer, and set a provider key such as OPENAI_API_KEY or ANTHROPIC_API_KEY. The provider is detected from the environment

smolagents

  1. Run CodeAgent with executor_type set to e2b, docker, modal or blaxel whenever the model or its inputs aren't trusted
  2. Use smolagents 1.24.0 or later to get the remote-executor deserialisation fix
  3. Set max_steps and final_answer_checks so a run stops on its own
  4. Pass structured_output explicitly to MCPClient to avoid the default-change warning
  5. Pin the version, since minor releases have removed APIs

Questions

Which is better for AI agents, AgentOS or smolagents?

AgentOS scores 75.8 (BB) on agent readiness against smolagents's 58.7 (C), and leads in 6 of 7 scored categories.

Are AgentOS and smolagents open source?

Yes. AgentOS is open source (Apache-2.0). smolagents is open source (Apache-2.0).

Other comparisons with AgentOS or smolagents

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.