Discofork
Repository brief

ChatGPTNextWeb/NextChat

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-30T13:07:19.609Z
3mo ago

ChatGPTNextWeb/NextChat

NextChat is a large, actively maintained open source AI assistant project: a light, fast chat app with support for web and desktop/mobile platforms. It has very high adoption signals (87,609 stars and 60,006 forks) and recent commits through 2025-09, with the repo still updated as of 2026-03-30. Forks are most interesting if you want a mature, multi-platform AI chat client with broad model/provider support, deployment options, and an existing enterprise/private-deployment direction.

GitHub
Loading tags...
Stars87,609
Forks60,006
Default branchmain
Last pushed2025-12-02T17:05:02Z
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

Choose this fork if you want NextChat as a LangChain-driven assistant platform with custom tools and retrieval. Choose upstream if you want the broadest model/platform coverage and the lowest maintenance burden.

Choose this fork if you want a materially redesigned NextChat with extra workflow features and accept that it is substantially behind and farther from upstream. If you want maximum provider freshness, compatibility, and easy backports, upstream is the safer base.

Choose this fork if you want a Gemini-branded product with marketing, legal, and ad workflows already baked in. Avoid it if you want the upstream NextChat ecosystem, because this fork is materially behind and appears to trade breadth and freshness for product specialization.

Prefer this fork if you want a customized, actively maintained NextChat derivative with provider-management and rendering improvements. Prefer upstream if you want the latest broad model support and the lowest long-term upgrade risk.

Choose this fork if Azure OpenAI is the only target and you value a narrowed integration over upstream breadth. Choose upstream NextChat if you want current features, multi-provider support, MCP, and an actively maintained codebase.

Choose this fork if Azure OpenAI support and api-version control matter more than staying current with upstream. Prefer upstream NextChat if you want the latest provider/model support and active maintenance.

Choose this fork if you want NextChat with small UX and deployment customization, not if you want meaningful new product features or a clearly maintained upstream-sync strategy.

Choose this fork only if its captcha and static-deployment patches solve a specific deployment problem for you. If you want the latest NextChat features, models, or active maintenance, upstream is the better default.

Treat this as an outdated mirror, not an actively differentiated fork. Choose upstream unless you specifically need this frozen 2023-era baseline or are willing to do a substantial rebase.

Choose this fork only if you want a mostly upstream NextChat deployment with separate branding and you are comfortable owning maintenance. If you want current model support and active upstream fixes, the upstream project is the better default.