Docker Agent vs Strands Agents

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.

Strands Agents 89

Framework reading (telemetry defaults, approvals, guardrails, sandboxing). No usage analytics found in either SDK, and OpenTelemetry is opt-in (25). Interrupts and the harness's interventions gate tool calls behind human approval or Cedar policies, but the default sandbox is the local host (16). Guardrails, PII redaction and trusted message history pages, with Bedrock Guardrails integration (13). OpenTelemetry traces for every model and tool call (15). The AWS Vulnerability Disclosure Program on HackerOne and three advisories in October 2026 published with fixed versions (20). 25+16+13+15+20 = 89.

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

Strands Agents 87

Python 1.64.0 and TypeScript 1.24.0 tagged on 4 November 2026 (30). Python 1.55.0 on 8 September, 1.61.0 on 14 October, 1.62.0 on 21 October and 1.63.0 on 30 October among many releases in 90 days (20). 664 open issues and 1,151 open issues and pull requests on 6 November, with 545 issues opened in the 90 days to 3 November. Of the 50 newest, 12 had a comment and 15 were closed, and 9 of the 40 newest open items carry a bug label. An issue-responder workflow runs on new issues (12). Both official SDKs are current (15). Dependency floors, security-audit workflows and CI passing on main (10). 30+20+12+15+10 = 87.

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

Strands Agents 72

Apache-2.0 (30). A library that stores session state where the developer configures it. The default FileSessionManager kept sessions world-readable in /tmp until 1.48.0, which the October advisories record and fix (20). A written deprecation policy with warnings and removal at majors, without a dated support window (16). Telemetry is opt-in and documented (20). 30+20+16+20 = 86.

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

Strands Agents 87

Framework reading. An MCPClient is passed straight to the agent in a few lines and its lifecycle is managed, with tool filtering per client (22). Conversation managers, turn limits, token budgets and cancellation bound each run (20). Stop reasons and typed events, and hooks that can retry a model or tool call (16). Retry strategies, session managers that persist and resume a conversation, and interrupts that resume where they paused (17). Two official languages, but the default provider is Bedrock, which needs AWS credentials and model access (12). 22+20+16+17+12 = 87.

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

Strands Agents 95

Framework reading. Typed Python and TypeScript APIs with a reference for each (25). llms.txt with a Markdown twin of every page (10). The llms.txt and docs say when to use Strands over a hand-written loop and when to take the harness rather than the SDK (18). Tools are typed from decorated functions or Zod schemas (15). Python and TypeScript examples on every page, stop reasons and hook events documented, with no catalogue of exceptions (12). Versioning page and tagged releases per package (15). 25+10+18+15+12+15 = 95.