Discofork
Repository brief

TauricResearch/TradingAgents

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T19:49:53.069Z
1mo ago

TauricResearch/TradingAgents

TradingAgents is an actively maintained Python framework for multi-agent, LLM-driven financial trading. It has very high fork and star counts, a recent v0.2.3 release, and frequent commits focused on model support, backtesting correctness, proxy support, and multi-language output. Forks are likely interesting if you care about agentic trading systems, LLM orchestration, or adapting a fast-moving research codebase.

GitHub
Loading tags...
Stars44,494
Forks8,056
Default branchmain
Last pushed2026-03-29T19:50:48Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Prefer this fork if you want a crypto-first TradingAgents variant with a web UI and deployment helpers. Prefer upstream if you need the newest model support, backtesting fixes, and active maintenance.

Prefer upstream unless you specifically want this older, unchanged snapshot. For active use, upstream is the better choice because this fork adds nothing and is far behind current TradingAgents maintenance.

Prefer this fork if you want an opinionated, user-facing trading assistant with dashboard, memory, and scheduling features. Prefer upstream if you want the newest model support, broader provider coverage, and the most current framework fixes.

Adopt this fork only if you specifically want an older frozen snapshot. For most users, upstream is the better choice because this fork has no unique features and is materially behind on active fixes and capabilities.

Choose this fork if you want TradingAgents in Traditional Chinese and prefer a more deployment-ready, localized starting point. Choose upstream if you want the newest trading-agent and model support, because this fork is significantly behind.

Prefer upstream unless you specifically need this older commit history. This fork adds no visible capabilities and is substantially behind on active maintenance and recent fixes.

Prefer upstream unless you specifically need a frozen historical baseline. This fork does not appear to add capabilities, and its value is mainly as a clean, low-divergence snapshot.

Prefer upstream unless you specifically want a frozen baseline for your own work. This fork does not appear to add capabilities, and it lags on recent trading, model, and backtesting improvements.

Choose upstream unless you specifically want a stable snapshot with no fork-specific changes. This fork does not add features; it mainly lags upstream and is best for pinning or private experimentation, not for adopters seeking improvements.

Choose this fork if you want more control over the trading-agent architecture and are comfortable owning merge drift. Stay on upstream if you want the newest provider support, backtesting fixes, and lower maintenance risk.