OpenBB-finance/OpenBB

Prefer this fork only if you need the older terminal-style OpenBB experience or want to preserve its recorded fixtures. For most adopters, upstream is the better choice because it is actively maintained and has newer platform, Workspace, MCP, and CLI work.

Choose this fork only if its added macro/research workflows are exactly what you need and you are willing to own the maintenance. For most adopters, upstream is the safer default because this fork is materially behind and likely to miss current bug fixes, integrations, and platform improvements.

Choose this fork only if you need its custom AI/automation and research-specific changes and are willing to own a large upstream gap. If you want the latest OpenBB platform, Workspace, CLI, and MCP improvements with lower maintenance cost, upstream is the safer default.

Choose this fork only if you specifically want the older OpenBB Terminal workflow and can accept being far behind upstream. For most adopters, upstream is the better default because it is active, broader in scope, and much better maintained.

Choose this fork only if you want a mostly untouched OpenBB mirror; otherwise upstream is the better default because this fork shows no added capability and is materially behind recent maintenance and feature work.

Prefer upstream unless you specifically want this fork as a starting template; it adds no visible value and is materially behind current OpenBB.

Adopt this only if you want the legacy terminal-centric fork and its packaging/setup tweaks. If you want the current OpenBB platform, Workspace integration, MCP support, and ongoing fixes, upstream is the better choice.

Prefer this fork only if you specifically want the older, customized research terminal and are prepared to own maintenance. If you want current OpenBB features, active support, and platform integration, upstream is the better default.

Choose this fork only if you want the old terminal-first experience or need to preserve legacy behavior. For most adopters, upstream OpenBB is the better choice because this fork is stale and materially behind on modern integrations, maintenance, and platform breadth.