AI generated
OvertChat (MIT, self-hosted): a chat app for the models you already run, with speech, search, and coding agents in the same install. I run vLLM on 10x 3090s and wanted a ChatGPT-style app my partner and family would actually use, without sending them to a hosted provider. Point OvertChat at vLLM, llama.cpp, Ollama, SGLang, LM Studio, or any OpenAI-compatible endpoint; hosted providers are optional. Web, desktop (macOS/Windows/Linux), Android, and iOS all talk to the same server. Accounts, chats, and files live in one SQLite file. No telemetry, MIT. What you get that matters for local models - Bundled Parakeet STT, Kokoro TTS, and live voice. CPU is enough; no API keys. - Bundled SearXNG search with keyless fallbacks. - Optional sandbox: Python over attached PDFs, spreadsheets, and images; stateless and offline. - Projects, memory, documents, OpenUI cards (charts/tables/forms), and MCP tools. - Coding agents through a Host Connector: Codex, Claude Code, OpenCode, Pi, Oh My Pi, and Hermes. Run them on your workstation or over SSH; drive them from the browser or phone. How it compares - Open WebUI: stronger if you want shared channels, knowledge bases, model evaluations, and extensions. OvertChat's difference is a bundled household setup: speech, live voice, and SearXNG installed and connected by the wizard instead of separate services, plus native desktop/mobile clients and coding-agent sessions. - LibreChat: stronger for custom assistants, tools, code execution, interactive content, and organizational access controls. OvertChat bundles speech/search and household accounts; LibreChat's self-hosted speech and SearXNG guides require running those services separately. Both are MIT; Open WebUI has branding conditions. - If you already have Open WebUI or LibreChat and only need a text box, switching may not be worth it. The reason to switch is the surrounding stack: voice, search, sandbox, apps, and agents in one install. How it's tested - 646 commits; releases v0.34.0, desktop v0.13.0, mobile v1.26.0. - CI on every push/PR: lint, typecheck, all workspace tests, connector journal-scale recovery, speech transport/codec tests, Windows launcher contracts, production container build/content checks, sandbox isolation under production flags, and voice engine isolation. - Playwright E2E smoke: OpenUI cards, project files, and Gmail/Calendar connectors/tools. - Running at home on 10x 3090s; household use is the real validation. - Built with Claude Code and Codex, but the test and release surface is the evidence that it isn't a weekend prototype. Feedback wanted: what would make this replace Open WebUI or LibreChat for your local setup? Especially model discovery across backends, speech latency on CPU, and agent handoff. Repo: https://github.com/yoloyash/overtchat Install: curl -fsSL https://overtchat.com/install | sh Comparison: https://github.com/yoloyash/overtchat/blob/main/docs/comparison.md CI: https://github.com/yoloyash/overtchat/actions