Head to head · Agent durable · October 2026 research run
Terse Durable Actors vs TradingAgents
Terse Durable Actors scores 69.6 (B) on agent readiness against TradingAgents's 65.1 (B), and leads in 3 of 7 scored categories. TradingAgents leads on security & auth and transparency & trust. Both do agent durable.
Best agent frameworks and SDKs · All 190 frameworks comparisons
Which one, for what
Best for Stateful actors for chat, collaboration and multi-agent coordination, as an open-source alternative to Cloudflare Durable Objects per its README.
Ahead on
- Schema & documentation, 81 against 61
- Agent ergonomics, 89 against 61
- Maintenance & community, 83 against 78
Also in its favour
- Free to start without a card
Watch for
Version 0.18.7, with no stable release and no changelog file in the repository
Best for Researchers who want a fixed multi-agent analysis of one listed instrument or crypto pair on a date, with point-in-time data for backtests, and who will run Python.
Ahead on
- Security & auth, 62 against 49
- Transparency & trust, 68 against 53
Watch for
No MCP client or MCP server, so an agent drives it only through Python or the CLI
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 Terse Durable Actors +28
Terse Durable Actors 89
Ten MCP tools with one-line descriptions (25). Cursor paging with stated limits (1 to 100, or 1 to 500 for requests) and filters by actor, outcome, log level, text and time window (20). Errors carry a code and a message, start limits return named codes with Retry-After, and invalid MCP input says which characters are allowed (14 of 20). Nine tools carry readOnlyHint and invoke_actor carries destructiveHint, but invocations have no idempotency key (15 of 20). Local development needs one command and no credential, with official TypeScript and Python SDKs and generated typed clients (15). Total 89.
TradingAgents 61
Framework reading, scored on what an outside agent needs to call it. No MCP client or server, so it can't be attached as tools; a run is four lines of Python (TradingAgentsGraph(config=...).propagate(ticker, date)) or one headless CLI command with flags (10 of 25). Analyst selection, debate and risk rounds (default 1), max_tool_rounds (20), max_recur_limit (100), article limits and --no-html size a run (14 of 20). A typed vendor error hierarchy separates unavailable from absent data, the headless CLI names the missing flag before a run starts, and an unparseable decision returns REVIEW rather than Hold (15 of 20). Checkpoint resume is opt-in, a backtest rerun with the same run_id skips finished cells, and settlement writes each decision once; nothing writes to an outside system (15 of 20). Sensible defaults, but the default provider is OpenAI's GPT-6 models with a key, and Python only (7 of 15).
Schema & documentation Terse Durable Actors +20
Terse Durable Actors 81
OpenAPI 3.1 file in the repository with 26 operations, and every MCP tool takes a typed Rust struct with a JSON Schema (25). Markdown docs in the repository, an AGENTS.md and an agent skill for setting up projects (10). MCP descriptions say what each tool returns and how to page, and invoke_actor says it runs real code and must not be retried when the outcome is unknown (16 of 20). Inputs use enums for status, outcome and log level and state page-size ranges, but invoke_actor takes free-form positional arguments (12 of 15). Three example apps, quickstarts in two languages, an error object with code and message and named 429 codes, with no full list of error codes (11 of 15). Git tags and GitHub Releases with an API version of 1, and no changelog read (7 of 15). Total 81.
TradingAgents 61
Framework reading. No API reference or docs site. Typed interfaces exist in the source, Pydantic models for the research manager's, trader's and portfolio manager's outputs and Annotated signatures on the twelve data tools, with no py.typed marker (10 of 25). The README and changelog are Markdown in the repository; no llms.txt (4 of 10). The README states limits plainly, that runs vary, which statements past-dated runs withhold and why, and that it is a research tool, not advice (15 of 20). Configuration is a plain dict of string keys, though environment overrides are coerced to the default's type and fail loudly on a bad value (8 of 15). Runnable Python and CLI examples throughout the README; the vendor error hierarchy is documented only in source docstrings (9 of 15). Dated changelog for every release from 0.1.0 with upgrade notes (15).
Transparency & trust TradingAgents +15
Terse Durable Actors 53
MIT, copyright 2026 Terse (30). Self-hosted state stays in your PostgreSQL database and GCS bucket per the self-hosting guide. Terse's terms and privacy policy, both dated 14 May 2026, describe an earlier product of flows and workspaces, give no retention periods and don't mention Terse Cloud (10 of 30). No deprecation policy found, and SECURITY.md says older releases get no backports (0 of 20). SDK invocation telemetry is off by default and writes to standard error when enabled, and request spans and platform events are exported only to a collector the operator configures. No call to Terse's own hosts was found in the runtime or SDK source (18 of 20). Total 58.
TradingAgents 68
The editorial half. Apache 2.0 (30). Local software. The README says where the memory log, checkpoints, cache, reports and ChatGPT sign-in file live, and names each data source and model provider a run calls. tauric.ai's privacy policy (effective 31 October 2026, re-read on 2 November) covers its hosted services, not the framework, and gives no retention periods (18 of 30). "Upgrading from" notes in a dated changelog list what was removed or moved, with no written deprecation policy, and 0.5.1 removed APIs without a deprecation period (8 of 20). The update check is disclosed in the README and changelog with an opt-out, and the code says what it sends; the README doesn't name api.tauric.ai (17 of 20).
Security & auth TradingAgents +13
Terse Durable Actors 49
One server secret, DURABLE_ACTORS_SECRET, as a bearer token for the API and MCP, plus an optional invoke-only key limited to public actor methods. With the secret unset the API is unauthenticated, which SECURITY.md warns about (15 of 30). The invoke-only key and the MCP read-only hints give some least privilege, with no confirmation step before invoke_actor (10 of 20). The OpenAPI file marks actor output as untrusted and to be rendered as plain text, with no guidance for agents on injected instructions (6 of 15). Request history, actor logs, WebSocket sessions and state versions tied to the request that saved them (12 of 15). SECURITY.md gives a private reporting address, security@useterse.ai. No bug bounty, certification or published advisories found (6 of 20). On GKE the self-hosting guide runs actors in gVisor sandbox pods with per-actor storage credentials. Total 49.
TradingAgents 62
Framework reading. 30 for what leaves the machine and how credentials are held, 20 for least privilege and approvals, 15 for prompt injection, 15 for audit and 20 for the security programme. Keys are read from the environment, and the package loads the nearest .env on import by walking up from the working directory. The ChatGPT sign-in uses PKCE and dynamic client registration, keeps tokens in a 0600 file and revokes them on logout. The only calls of its own are the interactive CLI's daily release and notice check, with no run data, off without a terminal or with TRADINGAGENTS_NO_UPDATE_CHECK=1. SEC EDGAR gets a placeholder contact address unless one is set (24 of 30). It places no orders and holds no broker credentials, the data tools only read, and every ticker is validated before it is used in a file path. No approval hooks, which nothing in it needs (14 of 20). News, Reddit and StockTwits text goes into prompts. The source names prompt injection as the reason for path validation, but no guidance on injection was found in the README (5 of 15). Saved reports record the run's settings and each agent's report, the memory log keeps every decision, and debug=True streams the graph (11 of 15). Security reports go to GitHub private vulnerability reporting per the issue template, and the changelog has Security sections for a langchain-core patch and a dependency removed over CVE-2026-22218. No SECURITY.md, no security.txt on tauric.ai (404 on 2 November), no bounty, and the repository's advisories page wasn't read (8 of 20). 24+14+5+11+8 = 62.
Maintenance & community Terse Durable Actors +5
Terse Durable Actors 83
v0.18.7 tagged on 18 November 2026, the day of the check (30). 118 tags since v0.1.0 on 2 September 2026, with eight between 15 and 18 November (20). 23 open issues, three of them with long threads (7, 9 and 15 replies) and most with none. Pull requests from five outside contributors were merged between 2 October and 3 November 2026, and CONTRIBUTING.md says GitHub issues are triaged into the team's tracker (10 of 25). Current official TypeScript and Python SDKs at 0.18.7. The MCP endpoint is self-hosted and not in the official registry, which was not searched (15). CI with pinned action versions and lockfiles for Bun, Cargo and uv (8 of 10). Total 83.
TradingAgents 78
0.7.1 on 27 October 2026 (30). Seven releases in the 90 days to 2 November, 0.4.0 (31 August), 0.5.0, 0.5.1, 0.5.2, 0.6.0, 0.7.0 and 0.7.1 (20). The earlier issue and pull request counts came from shields.io and are struck. On the clone, fixes cite issue numbers and each release credits the people who reported or fixed them (15 outside contributors in 0.7.1), but 251 of the 258 commits since 4 August are by one maintainer's accounts and reply times couldn't be read (13 of 25, as pipecat on clone evidence). No PyPI package; versions ship as GitHub releases with a wheel since 0.7.0 (8 of 15). CI with tests, lint and a clean-install check; dependencies set lower bounds only and no Dependabot configuration is in the repository (7 of 10). 30+20+13+8+7 = 78.
Score by category
| Category | Weight | Terse Durable Actors | TradingAgents | Edge |
|---|---|---|---|---|
| Reliability | 16% | 51 | 52 | TradingAgents +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 81 | 61 | Terse Durable Actors +20 |
| Agent ergonomics | 13% | 89 | 61 | Terse Durable Actors +28 |
| Security & auth | 14% | 49 | 62 | TradingAgents +13 |
| Payments & pricing | 10% | 90 | 90 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 83 | 78 | Terse Durable Actors +5 |
| Transparency & trust | 7% | 53 | 68 | TradingAgents +15 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 69.6/100 | B 65.1/100 |
Facts side by side
| Fact | Terse Durable Actors | TradingAgents |
|---|---|---|
| Kind | Agent framework | Agent framework |
| Vendor | Terse | Tauric Research |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | Streamable HTTP | |
| Auth | API key | API key |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | MIT | Apache-2.0 |
| Tools exposed | 10 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-18 | 2026-10-27 |
| Terms last updated | 2026-05-14 | 2026-10-23 |
| Privacy policy last updated | 2026-05-14 | 2026-10-23 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 368 stars | none |
How the scores have moved
Verdicts
Terse Durable Actors
Durable Actors gives coding agents ten compact MCP tools with read-only and destructive hints, a public OpenAPI 3.1 file and typed TypeScript and Python clients, under MIT with near-daily releases. It is pre-1.0 at 0.18.7, one server secret controls everything unless an invoke-only key is added, and Terse's policies predate Terse Cloud.
TradingAgents
An Apache 2.0 LangGraph framework at 0.7.1 with seven 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.
Before you call either
Terse Durable Actors
- Call
list_projectsfirst and pass itsprojectIdto every other tool - Never retry
invoke_actorwhen the outcome is unknown, because calls are not deduplicated and run real code - Set
DURABLE_ACTORS_SECRETbefore exposing a server beyond localhost, and send it as a bearer token - Give backends that only call actors the invoke-only key, not the server secret
- On 429
actor_start_rate_limited, wait for theRetry-Afterseconds before starting another actor
TradingAgents
- 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 - Guard on the REVIEW signal before mapping
propagate()'s decision to a rating; it means no rating could be parsed - Set SEC_EDGAR_USER_AGENT to the operator's own name and address before fetching US fundamentals
- Keep provider keys out of the working directory tree unless intended, since the package loads the nearest .env on import
- Treat the rating as model output for research; the framework places no orders and its results vary between runs
Questions
Which is better for AI agents, Terse Durable Actors or TradingAgents?
Terse Durable Actors scores 69.6 (B) on agent readiness against TradingAgents's 65.1 (B), and leads in 3 of 7 scored categories. TradingAgents leads on security & auth and transparency & trust.
Are Terse Durable Actors and TradingAgents open source?
Yes. Terse Durable Actors is open source (MIT). TradingAgents is open source (Apache-2.0).
Other comparisons with Terse Durable Actors or TradingAgents
- AgentOS vs Terse Durable Actors
- AgentOS vs TradingAgents
- Agno vs Terse Durable Actors
- Agno vs TradingAgents
- BoxLang AI vs Terse Durable Actors
- BoxLang AI vs TradingAgents
- Claude Agent SDK vs Terse Durable Actors
- Claude Agent SDK vs TradingAgents
- CrewAI vs Terse Durable Actors
- CrewAI vs TradingAgents
- Cursor Agent SDK vs Terse Durable Actors
- Cursor Agent SDK vs TradingAgents
- Docker Agent vs Terse Durable Actors
- Docker Agent vs TradingAgents
- Agent Development Kit (ADK) vs Terse Durable Actors
- Agent Development Kit (ADK) vs TradingAgents
- guilds.run vs Terse Durable Actors
- guilds.run vs TradingAgents
- LangGraph vs Terse Durable Actors
- LangGraph vs TradingAgents
- LlamaIndex Framework vs Terse Durable Actors
- LlamaIndex Framework vs TradingAgents
- Mastra vs Terse Durable Actors
- Mastra vs TradingAgents
- Microsoft Agent Framework vs Terse Durable Actors
- Microsoft Agent Framework vs TradingAgents
- OpenAI Agents SDK vs Terse Durable Actors
- OpenAI Agents SDK vs TradingAgents
- Pydantic AI vs Terse Durable Actors
- Pydantic AI vs TradingAgents
- smolagents vs Terse Durable Actors
- smolagents vs TradingAgents
- Strands Agents vs Terse Durable Actors
- Strands Agents vs TradingAgents
- TradingAgents vs AI SDK
- Terse Durable Actors vs AI SDK
Machine-readable
- This page as Markdown
/compare/terse-durable-actors-vs-tradingagents.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/terse-durable-actors.json·/api/v1/tools/tradingagents.json - From a terminal
anchor compare terse-durable-actors tradingagents(the CLI) - Over MCP
compare_tools {"a": "terse-durable-actors", "b": "tradingagents"}at/mcp, no key