Docker Agent vs TradingAgents

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.

TradingAgents

An Apache 2.0 LangGraph framework at 0.7.0 with six releases in 90 days, a dated changelog with upgrade notes, a public test matrix and point-in-time rules for historical runs. It has no MCP client or server, no PyPI package and no documentation beyond the README, and its output is a model-written rating that places no orders.

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

TradingAgents

1. Run headless with tradingagents --ticker <T> --date <YYYY-MM-DD> --analysts market,news,fundamentals --save --no-show; a missing answer stops the run and names the flag
2. Guard on the REVIEW signal before mapping propagate()'s decision to a rating; it means no rating could be parsed
3. Set SEC_EDGAR_USER_AGENT to the operator's own name and address before fetching US fundamentals
4. Keep provider keys out of the working directory tree unless intended, since the package loads the nearest .env on import
5. Treat the rating as model output for research; the framework places no orders and its results vary between runs