AgentOS vs TradingAgents

AgentOS

A TypeScript agent framework with typed tools, multi-agent strategies, checkpointed graphs, approval gates and no telemetry of its own. It is at 0.14.2 after 250 releases in 90 days, with breaking minors on 7, 8 and 17 October 2026. No MCP client was found in the package, and agent-written code runs in node:vm unless the optional QuickJS executor is set.

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.

AgentOS

1. Pin an exact version of @framers/agentos. Feature commits ship as patch releases while it is 0.x, and breaking changes ship as minors
2. Leave emergentConfig.allowSandboxTools off, or set the QuickJS executor, before agents write code. The default node:vm executor shares the host process
3. Pass your own ICheckpointStore to compile() for runs that must survive a restart. The default store is in memory
4. Set hitl.approvals.beforeTool for tools that write, and choose a handler. No approval gate is on by default
5. Use Node 22 or newer, and set a provider key such as OPENAI_API_KEY or ANTHROPIC_API_KEY. The provider is detected from the environment

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