TauricResearch/TradingAgents

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.