Head to head · Agent frameworks · October 2026 research run

Microsoft Agent Framework vs Terse Durable Actors

Microsoft Agent Framework scores 83.1 (A) on agent readiness against Terse Durable Actors's 69.6 (B), and leads in 5 of 7 scored categories. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Microsoft Agent Framework A

Best for Teams on Azure or .NET, and for teams moving off AutoGen or Semantic Kernel, that want MCP, approval, checkpointed workflows and OpenTelemetry in one SDK.

Ahead on

  • Reliability, 78 against 51
  • Schema & documentation, 95 against 81
  • Security & auth, 93 against 49
  • Maintenance & community, 91 against 83
  • Transparency & trust, 85 against 53

Also in its favour

  • Agent-ready, a grade of BB or better
  • No key needed to call it

Watch for

Changes marked [BREAKING] shipped in minor releases of released packages, including agent-framework-core in 1.22.0 on 15 October and 1.23.0 on 22 October 2026

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.

Also in its favour

  • No incidents deducted, where Microsoft Agent Framework 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.

Security & auth Microsoft Agent Framework +44

Microsoft Agent Framework 93

Framework reading, so SOC 2 isn't scored. A package and version User-Agent goes out on client requests by default, with a feature-usage token on Foundry and Azure OpenAI paths. Both are documented with opt-out variables, and the observability module says the framework contacts no external system itself, with message content in traces off by default (25). approval_mode on function and MCP tools, an MCP tool allow-list, and Hyperlight and Monty sandboxes for model-written code in beta. Tools run without approval unless set (20). An Agent Safety page treats model-supplied arguments as untrusted, and FIDES labels content and enforces policy before sensitive tools run, though it is experimental and Python only (15). OpenTelemetry traces, metrics and logs to any exporter (15). SECURITY.md routes reports to MSRC with a bounty programme and coordinated disclosure, CodeQL runs in CI and three advisories were published with fixed versions on 7 October 2026. Microsoft's security.txt still carries an Expires of 23 September 2026 on 1 November. On 1 November the repository's advisories list showed none to our reader, while the GHSA-9f26-7mqc-9vc4 page still loads as published on 7 October, so no advisory after 17 October was found (18).

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.

Transparency & trust Microsoft Agent Framework +32

Microsoft Agent Framework 85

MIT (30). The core README says what the User-Agent and feature token are, and a design spec in the repository says the token goes only to Foundry and Azure OpenAI pipelines and not to third-party providers. That spec is still marked proposed on 1 November, and we found no statement of how long Microsoft keeps the data and no privacy document for the framework (22). Package lifecycle states are published per package, experimental APIs raise warnings, breaking changes are dated in the Python changelog and there are upgrade guides, but we found no written support window (14). Telemetry is disclosed with two opt-out variables (20).

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.

Reliability Microsoft Agent Framework +27

Microsoft Agent Framework 78

Read with the local-software lines. Official packages on PyPI (Requires-Python >=3.10 in the repository, though 1.24.0 makes Python 3.11 the supported baseline and says the next release drops 3.10) and NuGet (net8.0 to net10.0, netstandard2.0, net472) (20). Of the 15 most recent .NET build and test runs on 1 November 2026, 10 passed, 2 were cancelled and 4 wait for approval on a pull request, with none failed, and the scheduled runs on main passed on 31 October and 1 November (25). 610 open issues and 229 open pull requests on 1 November, up from 575 and 201 on 8 October. Closures and bug labels weren't re-counted (10). The Python changelog follows Keep a Changelog and states semantic versioning, and marks breaking changes, but they keep shipping in minor releases of released packages, such as agent-framework-core in 1.22.0 on 15 October and 1.23.0 on 22 October 2026 (8). Python 1.24.0 and .NET 1.27.0, with the root and core packages classed 5 - Production/Stable (15).

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.

Schema & documentation Microsoft Agent Framework +14

Microsoft Agent Framework 95

Typed in both languages, with py.typed markers and API references for Python and .NET on Microsoft Learn (25). Learn returns each docs page as Markdown when asked with an Accept header. No llms.txt was found (10). The overview has a table for when to use an agent or a workflow, and says to write a function instead where one would do (20). Tools are Python functions typed with Annotated and Pydantic Field, or AIFunction in .NET (15). Samples for every area and a typed exception hierarchy in the source, but we found no exception reference in the docs pages we read (12). A dated Python changelog and four upgrade guides. No changelog file was found for .NET (13).

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.

Maintenance & community Microsoft Agent Framework +8

Microsoft Agent Framework 91

Python 1.24.0 and .NET 1.27.0, both tagged on 2026-10-30 (30). 22 release tags in the 90 days to 1 November, 11 Python and 11 .NET (20). 610 open issues and 229 open pull requests on 1 November, and triage, labelling and stale-ping workflows run on new issues. We couldn't see reply times (17). Python and .NET packages are current, and Go is a public preview line with v0.2.1 tagged on 27 October 2026 (15). CI, CodeQL and Dependabot run, though two of four Dependabot update runs failed on 8 October, per the 8 October check, not re-read on 1 November (9).

Terse Durable Actors 83

v0.18.7 tagged on 18 November 2026, the day of the check (30). 118 tags since v0.1.0 on 2 September 2026, with eight between 15 and 18 November (20). 23 open issues, three of them with long threads (7, 9 and 15 replies) and most with none. Pull requests from five outside contributors were merged between 2 October and 3 November 2026, and CONTRIBUTING.md says GitHub issues are triaged into the team's tracker (10 of 25). Current official TypeScript and Python SDKs at 0.18.7. The MCP endpoint is self-hosted and not in the official registry, which was not searched (15). CI with pinned action versions and lockfiles for Bun, Cargo and uv (8 of 10). Total 83.

Score by category

CategoryWeightMicrosoft Agent FrameworkTerse Durable ActorsEdge
Reliability16%7851Microsoft Agent Framework +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9581Microsoft Agent Framework +14
Agent ergonomics13%8789Terse Durable Actors +2
Security & auth14%9349Microsoft Agent Framework +44
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9183Microsoft Agent Framework +8
Transparency & trust7%8553Microsoft Agent Framework +32
Negative events≤15-50
TotalA 83.1/100B 69.6/100

Facts side by side

FactMicrosoft Agent FrameworkTerse Durable Actors
KindAgent frameworkAgent framework
VendorMicrosoftTerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicenceMITMIT
Tools exposednone10
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-302026-11-18
Terms last updatedno document linked2026-05-14
Privacy policy last updatedno document linked2026-05-14
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetyes
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity14k stars, 48k PyPI/wk368 stars
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Microsoft Agent Framework

Python 1.24.0 and .NET 1.27.0 are MIT, past 1.0 and released about weekly, with an MCP client, tool approval, checkpointed graph workflows and OpenTelemetry. Breaking changes ship in minor releases, a version User-Agent and a feature-usage token are sent by default, and a high-severity advisory in the .NET declarative workflows package was published on 7 October 2026.

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

Microsoft Agent Framework

  1. Pin exact versions. Minor releases have carried [BREAKING] changes, 1.23.0 moved MCP to the 2.x SDK, and 1.22.0 writes stored state older runtimes can't read, so read python/CHANGELOG.md first
  2. Set approval_mode="always_require" on tools and MCP servers that write. Tools run without approval unless set, and 1.24.0 warns when the MCP default is left implicit
  3. Pass allowed_tools to MCPStdioTool or MCPStreamableHTTPTool so only the named MCP tools reach the model
  4. Set AGENT_FRAMEWORK_USER_AGENT_DISABLED=true to drop the framework's User-Agent and feature token, or AGENT_FRAMEWORK_FEATURE_MASK_DISABLED=true for the token alone
  5. On .NET, use Microsoft.Agents.AI.Workflows.Declarative 1.24.0 or later. Earlier versions could forward protected workflow values to an external 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, Microsoft Agent Framework or Terse Durable Actors?

Microsoft Agent Framework scores 83.1 (A) on agent readiness against Terse Durable Actors's 69.6 (B), and leads in 5 of 7 scored categories.

Are Microsoft Agent Framework and Terse Durable Actors open source?

Yes. Microsoft Agent Framework is open source (MIT). Terse Durable Actors is open source (MIT).

Other comparisons with Microsoft Agent Framework 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.