Agno vs Docker Agent

Agno

An Apache 2.0 Python agent framework at 3.1.1 with an MCP client, tool confirmation and admin approvals, a durable job queue and 25 stable releases in 90 days. Usage telemetry is on by default with unhashed identifiers, and three high or critical advisories were published against it in the last 12 months, all fixed.

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 two high-severity approval bypasses were fixed in August and September 2026.

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

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