chat vs claude-quickstarts
Two of the top chat apps, side by side: score, setup, license, activity and what each review found.
chat
Nuxt UI chat template with GitHub login, SQLite history and AI Gateway
claude-quickstarts
Independent Claude API starter projects, one folder per pattern
| What we compare | chat | claude-quickstarts |
|---|---|---|
| Score parts, out of 100 | ||
| Adoption | 14, niche | 75, popular |
| Freshness | 100, active | 100, active |
| Maintenance | 33, patchy | 33, patchy |
| Easy to run | 67, easy | 0, hard |
| Agent-ready | 0, none | 40, minimal |
| Facts from GitHub and the README | ||
| Stars | 377 | 17.9k |
| License | MIT (permissive) | MIT (permissive) |
| Last commit | Oct 2026 | Oct 2026 |
| Last release | None published | None published |
| Language | Vue | TypeScript |
| Docker | No | No |
| GPU | Not needed | Not needed |
| arm64 or Apple Silicon | Not stated | Not stated |
chat
A Nuxt app on Nuxt UI and the AI SDK: streaming replies with reasoning, three models through Vercel AI Gateway (Claude Haiku 4.5, Gemini 3 Flash, GPT-5 Nano), provider web search, dictation over WebSocket, and chart and weather tool calls. GitHub OAuth, chat history in SQLite or Turso through Drizzle, and NuxtHub Blob uploads are included. For Vue and Nuxt teams who want a complete chat UI with persistence.
Who it is for: Vue and Nuxt teams who want a complete chat UI
Strengths
- Auth, Drizzle migrations and uploads wired; local dev needs no external database
- Blob storage swaps between local disk, Vercel Blob, Cloudflare R2 and S3
- Live demo and a one-command scaffold (npm create nuxt -t ui/chat)
- Committed within the last day
Weaknesses
- Models and dictation go through Vercel AI Gateway; direct keys need code changes
- Auth is GitHub OAuth only
- No tests listed
- Production database path assumes Turso
- Vue, ai-gateway, ai-sdk, anthropic, google
- Needs ai-gateway-api-key, github-oauth-app, sqlite-or-turso
- GitHub template
- env example file
claude-quickstarts
Independent Claude API starter projects in one repo, not one app: a customer support agent with a knowledge base, a financial data analyst with charts, computer-use and Playwright browser-use demos, a two-agent coding loop on the Agent SDK, and Managed Agents examples for Slack, Linear, Sentry, MCP and CopilotKit AG-UI. Mixed Next.js and Python, each folder with its own setup. For developers copying out one pattern.
Who it is for: Developers copying one Claude pattern into their own app
Strengths
- Covers computer use, browser use, Agent SDK and Managed Agents in one checkout
- Each quickstart is self-contained with its own README and setup
- Tracks current toolset shapes (computer_toolset_20260801, browser_toolset_20260801)
- Ships a CLAUDE.md for agent-driven edits
Weaknesses
- Not a single forkable app; you extract one subfolder
- No auth, billing or database at the root; only what each sample needs
- Anthropic-only; no provider abstraction
- No root .env.example or Docker files
- TypeScript, anthropic
- Needs anthropic-api-key
More in Chat apps
Building with these?
We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.