Head to head · Agent frameworks · October 2026 research run

Docker Agent vs Terse Durable Actors

Docker Agent scores 77.4 (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. Both do agent frameworks.

Best agent frameworks and SDKs · All 190 frameworks comparisons

Which one, for what

Docker Agent BB

Best for Teams already on Docker who want agents defined in a file, shared through an OCI registry and run the same way in a terminal, in CI or behind an HTTP, MCP or A2A server.

Ahead on

  • Reliability, 88 against 51
  • Schema & documentation, 90 against 81
  • Security & auth, 70 against 49
  • Maintenance & community, 96 against 83
  • Transparency & trust, 81 against 53

Also in its favour

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

Watch for

Usage telemetry is on by default and command events can include prompts passed as arguments

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 81

Also in its favour

  • No incidents deducted, where Docker Agent loses 7 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 Docker Agent +37

Docker Agent 88

Read with the local-software lines, because the owner runs it. Binaries for macOS, Linux and Windows on amd64 and arm64 on every GitHub release, a Homebrew formula at 1.154.0 on 1 November, a Docker Hub image updated on 31 October, and Docker Desktop 4.63 and later bundle it. Go 1.27 is the stated minimum for source builds (20). The ci workflow runs on every push to main with about 1,350 test files and an e2e directory. Nine of the last ten push runs passed on 8 October, per the 8 October check, not re-read on 1 November (25). 25 open issues and 17 open pull requests on 8 October, most labelled and answered, with open reports of a race in transfer_task (#4156), a hand-off dropped silently (#4242) and edit_file editing the first of several matches (#3929), per the 8 October check, not re-read on 1 November (20). The changelog has Breaking Changes sections, but those changes ship in minor releases (1.114.0, 1.133.0 and 1.137.0 since July) and the major version has never moved. Since then 1.152.0 (21 October) made --auth-token mandatory on non-loopback API listeners under Bug Fixes, and 1.153.0 (28 October) removed MCP sampling, roots and logging support under Technical Changes and changed Go runtime packages in commits marked !, none of them in a Breaking Changes section (8). 1.154.0, past 1.0 (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.

Transparency & trust Docker Agent +28

Docker Agent 81

Apache-2.0 (30). The telemetry page lists what's collected and warns that arguments and error text can carry secrets or personal data. It doesn't name the endpoint (api.docker.com, per the source), link Docker's privacy policy or give a retention period, unchanged on 17 October (15). Breaking changes are dated in the changelog and one renamed variable kept a fallback for one release, with no written deprecation policy, and the changelog says frozen config schema versions aren't maintained long-term (10). Telemetry is disclosed in the README, the docs and a first-start notice, with an opt-out variable (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.

Security & auth Docker Agent +21

Docker Agent 70

Framework reading. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Usage telemetry is on by default, with a notice on first start and TELEMETRY_ENABLED=false to stop it. The telemetry page, moved to the configuration section by 17 October, still says command events include positional arguments, which for run and exec can include prompts, and error text (12). Four safety modes with allow, ask and deny rules, a default that asks for anything not read-only, --exec rejecting unapproved calls, --sandbox for a Docker Sandboxes VM, and HTTP MCP defaulting to loopback and restricted. Since 1.152.0 (21 October) the API server rejects cross-origin requests, checks Host on unauthenticated listeners and requires --auth-token on non-loopback ones. A run's --listen control plane still has no built-in authentication and accepts loopback addresses and local sockets only (19). The docs treat skill files and third-party configs as untrusted and restrict URI schemes against prompt injection, with no dedicated guidance page (10). Hooks for audit logging and approval decisions, opt-in OpenTelemetry traces, NDJSON transcripts and a session database (14). SECURITY.md with a 72-hour acknowledgement, a valid security.txt on docker.com (expires 2030-01-01, re-read on 1 November), two advisories published on GitHub with fixed versions, and CodeQL and zizmor in CI. No paid bounty, and we saw no CVE identifiers on the advisories. The advisories page answered 403 on 1 November, the GitHub advisory database held no new docker-agent entry from August to November, and OSV lists none for the Go module. 1.152.0 updates Go to 1.27.3 for its security fixes and locks down the REST API against CSRF and DNS rebinding, with no advisory found for the latter (15). SOC 2 isn't scored for a framework.

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.

Maintenance & community Docker Agent +13

Docker Agent 96

v1.154.0 published on 2026-10-28 (30). 36 tagged releases in the 90 days from 3 August to 1 November, v1.120.0 to v1.154.0 (20). 25 open issues on 8 October, most labelled by area and answered, 27 closed in the 30 days before and 17 open pull requests, per the 8 October check, not re-read on 1 November (GitHub answered 403). We didn't measure reply times (21). The Homebrew formula was at 1.154.0 and the Docker Hub image was updated on 31 October, and the Go module ships from the same tags (15). Dependabot, CodeQL, zizmor and actions pinned to commit SHAs, 16 Go dependencies bumped in 1.153.0, with CI passing on main per the 8 October check (10).

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.

Schema & documentation Docker Agent +9

Docker Agent 90

Framework reading. agent-schema.json in the repository is a JSON Schema for the whole config, and the chat server serves its OpenAPI document at /openapi.json. We found no OpenAPI document for the native /api server and didn't check the Go package reference (22). llms.txt on docker.github.io/docker-agent and on docs.docker.com (10). The docs say when to use the API server and when the chat server, compare six ways to pass large input, and state that permissions aren't a security boundary (17). Configs are parsed strictly, unknown fields fail to load with a hint, and safety fields accept four named modes only (13). An examples directory, a troubleshooting page of common errors and documented HTTP status codes for the API. We found no exit-code reference for run --exec (13). A dated CHANGELOG.md and a numbered config schema, now version 16, with migration on load (15).

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.

Agent ergonomics Terse Durable Actors +8

Docker Agent 81

Framework reading, scored on what an agent with MCP needs. The README's agent with one MCP server is eight lines of YAML and no code, with deferred toolsets and a code mode (23). Budgets cap cost, tokens and time, tool results are bounded to 50 KiB since 1.148.0, and context is compacted, but max_iterations is unlimited and no budget applies unless declared (16). --json writes one NDJSON event per message, tool call and error, and the API documents 404, 409, 413 and 502 responses. No exit-code reference found for run --exec (14). Sessions resume from SQLite, the event stream replays from a sequence number, follow-ups accept an Idempotency-Key, and read-only and destructive tool annotations drive the safety modes (18). One binary and a model key or a local model are enough to start. The library is Go only (10).

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.

Score by category

CategoryWeightDocker AgentTerse Durable ActorsEdge
Reliability16%8851Docker Agent +37
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9081Docker Agent +9
Agent ergonomics13%8189Terse Durable Actors +8
Security & auth14%7049Docker Agent +21
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9683Docker Agent +13
Transparency & trust7%8153Docker Agent +28
Negative events≤15-70
TotalBB 77.4/100B 69.6/100

Facts side by side

FactDocker AgentTerse Durable Actors
KindAgent frameworkAgent framework
VendorDockerTerse
Hosted endpointno (local only)no (local only)
TransportsStreamable HTTP
AuthNoneAPI key
PricingFreeFreemium
x402nono
LicenceApache-2.0MIT
Tools exposednone10
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-11-18
Terms last updated2026-08-262026-05-14
Privacy policy last updated2026-08-262026-05-14
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesyes
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waiveryesnot found in the text
Popularity4k stars368 stars
Agent reviews2.8/5 (4)none

How the scores have moved

Verdicts

Docker Agent

An agent with an MCP server is eight lines of YAML, and the same file runs in a terminal, headless, or as an HTTP, MCP or A2A server. Usage telemetry is on by default and can carry prompts passed as command arguments, and breaking changes keep shipping in minor releases, two of them in October 2026 without a breaking label.

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

Docker Agent

  1. Set TELEMETRY_ENABLED=false before run or exec with a prompt on the command line. Telemetry is on by default and sends positional arguments
  2. For unattended runs pass --safety restricted with an allow-list, or --sandbox. Without a policy, --exec rejects every tool call that needs approval
  3. Set max_iterations and a budget block in the config. Both are unlimited by default
  4. Run 1.130.0 or later. Earlier versions ran shell commands embedded in local skills, and A2A sessions before 1.126.0 skipped tool approval
  5. Review runtime.safety in any config pulled from a registry or URL. An author default of autonomous runs every tool call unprompted
  6. Pass --auth-token to serve api on any non-loopback address from 1.152.0, or it won't start. Don't rely on MCP sampling, removed in 1.153.0

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, Docker Agent or Terse Durable Actors?

Docker Agent scores 77.4 (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.

Are Docker Agent and Terse Durable Actors open source?

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

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