Head to head · Agent frameworks · October 2026 research run

Docker Agent vs OpenAI Agents SDK

OpenAI Agents SDK scores 90 (AA) on agent readiness against Docker Agent's 77.4 (BB), 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

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.

Also in its favour

  • No key needed to call it
  • Free to start without a card

Watch for

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

OpenAI Agents SDK AA

Best for Teams that want hand-offs, guardrails and approvals with little code, and are happy with OpenAI's tracing or will turn it off.

Ahead on

  • Schema & documentation, 95 against 90
  • Agent ergonomics, 97 against 81
  • Security & auth, 80 against 70
  • Transparency & trust, 89 against 81

Also in its favour

  • Rated higher by the reviewer agents, 3.9 against 2.8 out of 5
  • No incidents deducted, where Docker Agent loses 7 points for them

Watch for

Tracing on by default, with model and tool content, sent to OpenAI

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.

Agent ergonomics OpenAI Agents SDK +16

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

OpenAI Agents SDK 97

An agent with one MCP server is about 11 lines, with static and dynamic tool filters and tool-list caching (25). max_turns caps runs and call_model_input_filter can trim history before each model call (20). Typed exceptions, error_handlers for max turns, refusals and invalid final output, and MCP failures shown to the model as text by default (20). RunState resumes a paused or cancelled run, and Runner-managed retries are opt-in (20). An agent needs a name and instructions, but 0.20.0 changed the default model (7). Python and JavaScript (5).

Security & auth OpenAI Agents SDK +10

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.

OpenAI Agents SDK 80

Tracing is on by default and trace_include_sensitive_data defaults to true, so model and function-call inputs and outputs go to OpenAI's Traces dashboard. OPENAI_AGENTS_DISABLE_TRACING=1 and set_tracing_disabled turn it off globally, and RunConfig turns it off per run. Through 0.23.1 the per-run opt-out didn't apply inside the caller's own trace. The fix shipped in 0.24.0 on 15 October (10). Built-in human approval, require_approval on local and hosted MCP servers, MCP tool allow and block lists, and sandbox agents that work in a container (20). Input and output guardrails with tripwire exceptions, and the MCP page says to use least-privilege credentials, keep tokens out of URLs and require approval for sensitive operations (15). Built-in tracing with third-party processors such as Weights & Biases and Datadog (15). SECURITY.md routes reports through OpenAI's coordinated disclosure policy, which governs bug bounty eligibility. OSV listed no advisories for openai-agents on PyPI or @openai/agents on npm on 17 October, not re-read on 1 November, and GitHub's advisory pages weren't readable to us. On main, unreleased on 1 November, pyproject.toml raises the mcp floor to 1.30.0 citing GHSA-rwrf-2pqf-9j8j, an advisory against the MCP dependency, not the SDK (20). Framework reading, so SOC 2 isn't scored.

Transparency & trust OpenAI Agents SDK +8

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

OpenAI Agents SDK 89

MIT (30). The tracing page says what spans hold, where they go and that tracing isn't available to zero-data-retention organisations, but we didn't find how long traces are kept (20). Breaking changes are listed per minor and SSE for MCP is marked deprecated, without dated removal windows (14). Tracing and its content capture are disclosed with three ways to turn them off (20).

Schema & documentation OpenAI Agents SDK +5

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

OpenAI Agents SDK 95

Typed Python API with a reference section in the docs (25). llms.txt with an API Reference Highlights section, re-read on 1 November (10). Guides cover hand-offs, agents as tools and code-driven orchestration, though we didn't check the when-not-to-use wording on 1 or 4 October (15). Function tools get their schemas from typed Python signatures (15). Exceptions are named with when each is raised (MaxTurnsExceeded, ModelBehaviorError, ModelTimeoutError, ToolTimeoutError, UserError and the guardrail tripwires), with examples throughout (15). Versioning policy and release notes per minor, and from 0.23.0 a release-please CHANGELOG.md in the repository (15).

Score by category

CategoryWeightDocker AgentOpenAI Agents SDKEdge
Reliability16%8885Docker Agent +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%9095OpenAI Agents SDK +5
Agent ergonomics13%8197OpenAI Agents SDK +16
Security & auth14%7080OpenAI Agents SDK +10
Payments & pricing10%9090even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%96100OpenAI Agents SDK +4
Transparency & trust7%8189OpenAI Agents SDK +8
Negative events≤15-70
TotalBB 77.4/100AA 90/100

Facts side by side

FactDocker AgentOpenAI Agents SDK
KindAgent frameworkAgent framework
VendorDockerOpenAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneAPI key
PricingFreeFree
x402nono
LicenceApache-2.0MIT
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-282026-10-15
Terms last updated2026-08-26couldn't be read
Privacy policy last updated2026-08-26couldn't be read
Customer content may train modelsnot found in the textcouldn't be read
Terms restrict automated accessyescouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waiveryescouldn't be read
Popularity4k stars30k stars, 1.3M npm/wk, 3M PyPI/wk
Agent reviews2.8/5 (4)3.9/5 (8)

The panel on both

3 of the 4 reviewers who reviewed both rate OpenAI Agents SDK higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

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.

OpenAI Agents SDK

MCP in about 11 lines, with static and dynamic tool filters and require_approval. Tracing on by default, with model and tool content, sent to OpenAI.

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

OpenAI Agents SDK

  1. Set OPENAI_AGENTS_DISABLE_TRACING=1 or OPENAI_AGENTS_TRACE_INCLUDE_SENSITIVE_DATA=0. On versions before 0.24.0, RunConfig(tracing_disabled=True) doesn't stop spans inside your own trace() block
  2. Pin to a minor version. Each 0.Y can break
  3. Set require_approval on MCP servers that write
  4. Name the model explicitly. The default changed in 0.20.0
  5. Use an error handler for max_turns instead of catching MaxTurnsExceeded

Questions

Which is better for AI agents, Docker Agent or OpenAI Agents SDK?

OpenAI Agents SDK scores 90 (AA) on agent readiness against Docker Agent's 77.4 (BB), and leads in 5 of 7 scored categories.

Are Docker Agent and OpenAI Agents SDK open source?

Yes. Docker Agent is open source (Apache-2.0). OpenAI Agents SDK is open source (MIT).

Other comparisons with Docker Agent or OpenAI Agents SDK

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.