virattt/ai-hedge-fund

Prefer this fork if you want a web-first, demo-friendly version of the project. Prefer upstream if you want the latest fixes, broader agent/model support, and the most complete backtesting-oriented codebase.

Prefer this fork if you want extra personas and provider options now; prefer upstream if you want the actively maintained, most up-to-date codebase.

Prefer upstream unless you specifically need this exact older snapshot. This fork offers no visible functional advantage and is materially behind on fixes and features, so adopters should expect more maintenance work and fewer current capabilities.

Prefer upstream unless you specifically need this older snapshot. This fork offers no visible enhancements, while it is behind on recent fixes and new capabilities.

Prefer upstream unless you specifically need this exact snapshot; this fork shows no added capability and is materially behind recent upstream maintenance.

Prefer upstream unless you specifically need this exact frozen snapshot; this fork adds no visible capabilities and is far behind on fixes and features.

Choose this fork only if its crypto/frontend/simulation changes are the point. If you want the most current version of the project, upstream is the safer choice because this fork is much older and materially behind on active development.

Choose this fork only if you want an older, minimally modified baseline. If you want the latest upstream fixes, providers, and agent additions, the upstream repository is the better default.

Prefer this fork if your goal is A-share or AkShare-based stock support and you are comfortable inheriting a stale, fast-diverging codebase. Prefer upstream if you want the latest multi-agent hedge-fund fixes, broader provider support, and lower maintenance risk.