Head to head · Agent frameworks · October 2026 research run

Agno vs Terse Durable Actors

Agno scores 74 (BB) on agent readiness against Terse Durable Actors's 69.6 (B), and leads in 5 of 7 scored categories. Terse Durable Actors leads on agent ergonomics and payments & pricing. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Agno BB

Best for Python teams that want agents, teams and workflows plus a self-hosted server with REST, MCP, approvals and scheduling in one package.

Ahead on

  • Reliability, 83 against 51
  • Schema & documentation, 90 against 81
  • Security & auth, 64 against 49
  • Transparency & trust, 84 against 53

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Usage telemetry is on by default and sends session, run and agent identifiers unhashed. Prompts and outputs are not sent

Terse Durable Actors B

Best for Stateful actors for chat, collaboration and multi-agent coordination, as an open-source alternative to Cloudflare Durable Objects per its README.

Ahead on

  • Agent ergonomics, 89 against 76
  • Payments & pricing, 90 against 75

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Agno loses 5 points for them

Watch for

Version 0.18.7, with no stable release and no changelog file in the repository

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.

Reliability Agno +32

Agno 83

Official PyPI package with Python 3.9 or later stated (20). Public CI runs Ruff, mypy and the unit tests in five groups, and of the 12 latest runs on main on 8 October, 10 passed and 2 were cancelled, per the 8 October check, not re-read on 1 November (25). 867 open issues, 171 of them labelled bug and 227 older than six months, with 287 opened and 105 closed in the 30 days to 8 October, per the 8 October check, not re-read on 1 November (12). Majors 2.0 and 3.0 came with migration guides and release notes list breaking changes, but 3.1.0, a minor, shipped a breaking filesystem table re-key (11). Version 3.1.12 with the Production/Stable classifier (15). Local-software reading.

Terse Durable Actors 51

Graded as local software, the runtime and SDKs you run yourself. The README and the Python SDK README install with bunx durable-actors or uvx --from 'durable-actors[cli]' and state Bun 1.4.2+ and Python 3.11+, and the release workflow publishes to npm. The registry pages were not read (15 of 20). A public CI workflow runs Rust, Python, TypeScript and example builds on every push and pull request. Whether it passes on main was not checked (15 of 25). 23 issues were open on 18 November 2026, mostly improvements and feature requests, with a few bug reports such as a constructor that keeps its SQLite writes after throwing (17 November) and alarms that run more than once (11 November) (18 of 25). Release notes are generated from pull-request labels on GitHub Releases, which were not read, and no changelog file or breaking-change notes were found in the repository (3 of 15). Version 0.18.7, not 1.0 or declared stable (0). Total 51.

Transparency & trust Agno +31

Agno 84

Apache 2.0 (30). The telemetry page lists the fields sent and says identifiers are not hashed, and the pricing page says the control plane holds no copy of customer data. The terms and privacy pages render only with JavaScript and were not read, and no retention period for telemetry was found (15). Migration guides for 2.0 and 3.0 and migration notices on what was removed, with no written deprecation policy found (10). Telemetry is disclosed in the README and docs with an opt-out, though the environment variable does not cover AgentOS or evals (18).

Terse Durable Actors 53

MIT, copyright 2026 Terse (30). Self-hosted state stays in your PostgreSQL database and GCS bucket per the self-hosting guide. Terse's terms and privacy policy, both dated 14 May 2026, describe an earlier product of flows and workspaces, give no retention periods and don't mention Terse Cloud (10 of 30). No deprecation policy found, and SECURITY.md says older releases get no backports (0 of 20). SDK invocation telemetry is off by default and writes to standard error when enabled, and request spans and platform events are exported only to a collector the operator configures. No call to Terse's own hosts was found in the runtime or SDK source (18 of 20). Total 58.

Security & auth Agno +15

Agno 64

Telemetry is on by default. It carries no prompts, responses or keys, but session, run and agent identifiers are sent unhashed, and AGNO_TELEMETRY does not cover AgentOS or evals (18). Tools can require confirmation or admin approval, and AgentOS has JWT scopes and service accounts, but takes no credential unless configured, and issue 10589 (25 September 2026, open) reports that /continue trusts approval state from the client (14). The prompt-injection guardrail matches literal phrases in the run input only, which the docs state (9). OpenTelemetry tracing, run history and an audit log in the 3.1 authorisation package (13). A valid security.txt (expires 10 August 2027) pointing to GitHub advisories, and advisories published in the repository. No SECURITY.md, no bounty found, and the trust centre was not read (10). Framework reading.

Terse Durable Actors 49

One server secret, DURABLE_ACTORS_SECRET, as a bearer token for the API and MCP, plus an optional invoke-only key limited to public actor methods. With the secret unset the API is unauthenticated, which SECURITY.md warns about (15 of 30). The invoke-only key and the MCP read-only hints give some least privilege, with no confirmation step before invoke_actor (10 of 20). The OpenAPI file marks actor output as untrusted and to be rendered as plain text, with no guidance for agents on injected instructions (6 of 15). Request history, actor logs, WebSocket sessions and state versions tied to the request that saved them (12 of 15). SECURITY.md gives a private reporting address, security@useterse.ai. No bug bounty, certification or published advisories found (6 of 20). On GKE the self-hosting guide runs actors in gVisor sandbox pods with per-actor storage credentials. Total 49.

Payments & pricing Terse Durable Actors +15

Agno 75

No payment protocol (0). Self-hosted rule, with the paid option scored. The control plane has public plan prices, Free at $0 and Pro at $150 a month, with Enterprise by quote (10). The package installs with no card (20) and runs with no Agno account (20). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 50 is 75.

Terse Durable Actors 90

Read with the self-hosted rule, with the price line for Terse Cloud. No x402, MPP or L402 in the repository (0). Terse Cloud publishes per-second prices without a login, US$0.00001971 per CPU and US$0.00000667 per GiB of memory requested (30). The MIT runtime is free to run with no card (30). An agent can start the runtime locally with no signup (30). Total 90.

Agent ergonomics Terse Durable Actors +13

Agno 76

An agent with an MCP server is about ten lines through MCPTools, with include_tools, exclude_tools and tool_name_prefix (22). tool_call_limit exists but defaults to None, and sessions, history and compression are configurable (14). A typed exception hierarchy, with RetryAgentRun and StopAgentRun to steer the loop from a tool (16). Runs continue by run ID after a pause and AgentOS has a durable queue, which is off by default (16). Few required parameters, Python only (8).

Terse Durable Actors 89

Ten MCP tools with one-line descriptions (25). Cursor paging with stated limits (1 to 100, or 1 to 500 for requests) and filters by actor, outcome, log level, text and time window (20). Errors carry a code and a message, start limits return named codes with Retry-After, and invalid MCP input says which characters are allowed (14 of 20). Nine tools carry readOnlyHint and invoke_actor carries destructiveHint, but invocations have no idempotency key (15 of 20). Local development needs one command and no credential, with official TypeScript and Python SDKs and generated typed clients (15). Total 89.

Schema & documentation Agno +9

Agno 90

A class reference under docs.agno.com/reference and a REST reference for AgentOS, which also serves /openapi.json (25). llms.txt with 3,985 lines, llms-full.txt, a Markdown twin of each page and a docs MCP server (10). Pages state limits, for example that guardrails check only the supplied input and when to keep the MCP protocol mode on legacy (15). Pydantic-typed classes and tool signatures, with a py.typed marker (13). Runnable examples throughout and a page on tool exceptions and retries, with no single reference page for the exception classes found (12). Dated changelog and release notes per version (15). Framework reading.

Terse Durable Actors 81

OpenAPI 3.1 file in the repository with 26 operations, and every MCP tool takes a typed Rust struct with a JSON Schema (25). Markdown docs in the repository, an AGENTS.md and an agent skill for setting up projects (10). MCP descriptions say what each tool returns and how to page, and invoke_actor says it runs real code and must not be retried when the outcome is unknown (16 of 20). Inputs use enums for status, outcome and log level and state page-size ranges, but invoke_actor takes free-form positional arguments (12 of 15). Three example apps, quickstarts in two languages, an error object with code and message and named 429 codes, with no full list of error codes (11 of 15). Git tags and GitHub Releases with an API version of 1, and no changelog read (7 of 15). Total 81.

Score by category

CategoryWeightAgnoTerse Durable ActorsEdge
Reliability16%8351Agno +32
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9081Agno +9
Agent ergonomics13%7689Terse Durable Actors +13
Security & auth14%6449Agno +15
Payments & pricing10%7590Terse Durable Actors +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8683Agno +3
Transparency & trust7%8453Agno +31
Negative events≤15-50
TotalBB 74/100B 69.6/100

Facts side by side

FactAgnoTerse Durable Actors
KindAgent frameworkAgent framework
VendorAgno Inc.Terse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthAPI keyAPI key
PricingFreeFreemium
x402nono
LicenceApache-2.0MIT
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-292026-11-18
Terms last updatedcouldn't be read2026-05-14
Privacy policy last updatedcouldn't be read2026-05-14
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readyes
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity43k stars, 476k PyPI/wk368 stars
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Agno

An Apache 2.0 Python agent framework at 3.1.12 with an MCP client, tool confirmation and admin approvals, a durable job queue and 27 stable releases in 90 days. Usage telemetry is on by default with unhashed identifiers, and 3.1.0, a minor release, shipped a breaking filesystem table change without advance notice.

Terse Durable Actors

Durable Actors gives coding agents ten compact MCP tools with read-only and destructive hints, a public OpenAPI 3.1 file and typed TypeScript and Python clients, under MIT with near-daily releases. It is pre-1.0 at 0.18.7, one server secret controls everything unless an invoke-only key is added, and Terse's policies predate Terse Cloud.

Before you call either

Agno

  1. Set AGNO_TELEMETRY=false before the first run, and pass telemetry=False to AgentOS and to each eval, which ignore the variable
  2. Configure JWT_VERIFICATION_KEY with AgentOS authorisation switched on, or OS_SECURITY_KEY, before exposing AgentOS. With neither set, REST and MCP routes take no credential
  3. Mark tools that write with requires_confirmation, and resume with continue_run once every requirement is resolved
  4. Set tool_call_limit on agents. The default is None
  5. Install extras for what you use, such as agno[mcp] for MCPTools and agno[os,mcp] for AgentOS with its MCP server

Terse Durable Actors

  1. Call list_projects first and pass its projectId to every other tool
  2. Never retry invoke_actor when the outcome is unknown, because calls are not deduplicated and run real code
  3. Set DURABLE_ACTORS_SECRET before exposing a server beyond localhost, and send it as a bearer token
  4. Give backends that only call actors the invoke-only key, not the server secret
  5. On 429 actor_start_rate_limited, wait for the Retry-After seconds before starting another actor

Questions

Which is better for AI agents, Agno or Terse Durable Actors?

Agno scores 74 (BB) on agent readiness against Terse Durable Actors's 69.6 (B), and leads in 5 of 7 scored categories. Terse Durable Actors leads on agent ergonomics and payments & pricing.

Are Agno and Terse Durable Actors open source?

Yes. Agno is open source (Apache-2.0). Terse Durable Actors is open source (MIT).

Other comparisons with Agno or Terse Durable Actors

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.