NextChat

ChatGPTNextWeb/NextChat

✨ Zero-config AI chat assistant. No API key needed — sign up and instantly chat with GPT-5, Claude 4, Gemini 2.5, DeepSeek & 100+ top models. Pay-as-you-go saves you more. Available on Web, iOS, macOS, Android, Linux, Windows.

Ship status

Slowed

Last push 31–120 days ago. Quiet, not gone.

Last push
Aug 11, 2026
53 days ago
Ship score
35/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 88,620 → 88,824 (Aug 18 – Sep 29, 2026)
+149 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
88.8K
Forks
58.9K
Open issues
850
Watchers
494
Primary language
TypeScript
Created
Mar 10, 2023
Owner
ChatGPTNextWeb · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 208 startups in the directory ship primarily in TypeScript.

Topics

#calclaude#chatgpt#claude#cross-platform#desktop#fe#gemini#gemini-pro#gemini-server#gemini-ultra#gpt-4o#groq#nextjs#ollama#react#tauri#tauri-app#vercel#webui

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 98%, self-hostable 49%, hosted offering 75%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: slowed — last push 2026-08-11This is the badge for ChatGPTNextWeb/NextChat, as served from the URL below.
[![OSSEAN: slowed](https://ossean.com/badge/ChatGPTNextWeb/NextChat.svg)](https://ossean.com/ChatGPTNextWeb/NextChat)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.