better-chatbot

Ochiq manbalardan

Avval Better Chatbot nomi bilan tanilgan. Navigator — agentlar, MCP va ish jarayonlarini avtomatlashtirish uchun ochiq manbali AI ish maydoni.

Mashina tarjimasi · Asl matnni koʻrsatish

Formerly Better Chatbot. Navigator is an open-source AI workspace for agents, MCP and workflow automation.

MCP serverKategoriya: MCP serverlar · SDK va freymvorklarOpen sourcemaʼlumot tekshirilgan: 15-okt, 2026

Sharh

  • agent
  • ai
  • ai-chatbot
  • automation
  • chatbot
  • claude
  • gemini
  • low-code
  • mcp
  • mcp-client

Oʻrnatish

Buyruqlar faqat koʻrsatiladi, marketpleys ularni bajarmaydi. Rasmiy hujjatlar bilan solishtiring.

Moslik

«Nomaʼlum» dalil topilmaganini bildiradi, mahsulot mos emasligini emas.
PlatformaHolatArxitekturaDalilIshonchlilik
Claude (web & desktop)Nomaʼlum———
Claude CodeNomaʼlum———
CursorNomaʼlum———
VS CodeNomaʼlum———
WindsurfNomaʼlum———
ChatGPTNomaʼlum———

Relizlar

tekshirilgan: 29-okt, 2026
v1.26.0Oxirgi22-noy, 2025Rasmiy manba ↗

1.26.0 versiyasi fayllari

Relizga fayllar biriktirilmagan.

Relizlar tarixi

Sifat profili

algoritm quality-v1.0 · baholangan 15-okt, 2026
Sifat bahosi93
Xavf bahosi0
Ishonchlilik 1.00
Sifat bahosi va xavf bahosi — turli koʻrsatkichlar. Yuqori sifat xavfsizlikni kafolatlamaydi.

Baho tarkibi

Qoʻllab-quvvatlash · 2016
last activity 57 days ago
Hujjatlar · 1515
README 18370 chars, description present
Foydalanishga tayyorlik · 1515
install instructions: yes; releases: yes
Metamaʼlumotlar · 1010
4/4 of description, homepage, license, topics
Relizlar · 1010
10 release(s), latest 327 days ago
Kategoriya aniqligi · 1010
classifier confidence 0.97
Ommaboplik · 108
1189 stars (log-dampened, 10k = max)
Litsenziya aniqligi · 55
SPDX MIT
Hamjamiyat · 55
issues enabled, 350 forks

Litsenziya

MIT
Litsenziya maʼlumrepozitoriy xostingi maʼlumotlariga koʻra

Bu katalog siyosati holati, yuridik xulosa emas.

Manbalar

github.com/keinsaasforever/better-chatbotAsosiy★ 1 189 yulduzfaollik: 19-avg, 2026Asosiy repozitoriy · Ishonchlilik 1.00

Sharhlar

Sharh yozish uchun kiring

Hali sharhlar yoʻq.

Muqobillar

README

keinsaasforever/better-chatbot dan · litsenziya MIT · yuklangan 29-okt, 2026

better-chatbot

An open-source AI chat and agent platform you can host yourself.

Talk to any model, attach your files, connect MCP tool servers, build workflows, and give agents a place to work — on infrastructure you control.

[License: MIT] [Discord]


Deploy to Vercel

[Deploy with Vercel]

One click, one value. The button clones the repository, provisions a Neon Postgres database, and asks for a single secret — any long random string (openssl rand -base64 32). The schema is created during the build, and models run through the Vercel AI Gateway on your Vercel account with no API key. Open the deployment and create an account; the first one becomes the administrator.

Details and optional features: docs/self-hosting.md.


Quick start (Docker)

Three variables. That is the whole configuration to get chatting:

git clone https://github.com/keinsaasforever/better-chatbot.git
cd better-chatbot
cp .env.example .env
POSTGRES_URL=postgres://postgres:postgres@postgres:5432/better_chatbot
BETTER_AUTH_SECRET=   # npx @better-auth/cli@latest secret
AI_GATEWAY_API_KEY=   # https://vercel.com/ai-gateway
docker compose -f docker/compose.yml up -d --build

Open http://localhost:3000 and create an account. The first account becomes the administrator.

Why one model key? Models are served through the Vercel AI Gateway, which fronts Anthropic, OpenAI, Google, Mistral, xAI, DeepSeek, Moonshot and more. You manage one key and one bill instead of seven, and you can switch models mid-conversation without touching configuration. If you would rather not use a gateway at all, point the app at Ollama, LM Studio, or any OpenAI-compatible endpoint — see Models.

Prefer running it directly? See docs/self-hosting.md.


What you get

Chat that does things. Streaming conversations with tool calling, file attachments, image generation, and a sandboxed code runner. Mention an agent, workflow, or tool with @ to pull it into the conversation.

Agents. Give an agent a role, instructions, and a set of tools. Share it with your workspace or keep it private.

Skills. Reusable capabilities an agent loads on demand, so a large toolbox does not have to sit in every prompt.

Projects with retrieval. Group chats, documents, and tools around a piece of work. Uploaded documents are chunked, embedded, and searched with pgvector — no external service required. Point a project at a knowledge base if you want hosted retrieval instead.

Workflows. Build a graph of steps — LLM calls, conditions, HTTP requests, code, templates — in a visual editor, publish it as a tool, and call it from any chat.

MCP tool servers. Connect any Model Context Protocol server over HTTP or stdio, with OAuth support, per-tool customization and a cached tool list. Self-hosted instances can run stdio servers; the desktop app runs them locally.

Scheduled tasks. Have an agent run on a schedule and report back.

Voice. Realtime voice conversations through the gateway, plus transcription.

Desktop app. An Electron build that adds local MCP servers, filesystem access, and the system keychain.

Model routing. Pick a model per message, or let the router choose from the catalog based on the task.


Upgrading from 1.x

This is a new major version. The layout is now a monorepo, the environment is different, and the schema has moved on considerably.

Back up your database first. Then:

pnpm install
pnpm tsx scripts/upgrade/from-better-chatbot-1.ts --dry-run
pnpm tsx scripts/upgrade/from-better-chatbot-1.ts --yes

The upgrade preserves your users, chats, agents, MCP servers and workflows. Archives become projects, and the threads inside them stay linked. It is a one-way migration — this is why the backup matters.

If you were setting per-provider API keys (OPENAI_API_KEY, ANTHROPIC_API_KEY and friends), replace them with a single AI_GATEWAY_API_KEY, or configure a local provider.


Setup

Vercel

The Deploy button above. Setting up an existing clone by hand is described in docs/self-hosting.md.

Docker Compose

The quick start above. The bundled stack includes Postgres with pgvector. Add --profile redis if you want resumable chat streams.

Local development

pnpm install            # writes .env from .env.example
pnpm docker:pg          # Postgres with pgvector on :5432
pnpm db:migrate         # apply the schema
pnpm dev                # http://localhost:3000

Postgres must have the pgvector extension — document embeddings are stored as vector(1536). The bundled image has it; managed Postgres usually offers it as a toggle.

Useful commands:

CommandWhat it does
pnpm checkLint, typecheck and unit tests — run before committing
pnpm test:e2ePlaywright end-to-end tests
pnpm db:migrateApply pending migrations
pnpm db:studioBrowse the database
pnpm docker:redisRedis for resumable streams

Optional integrations

Everything below is off until you configure it. The server prints which features are disabled at startup, so you always know why something is missing.

FeatureSetWithout it
File uploadsSUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, NEXT_PUBLIC_SUPABASE_URLAttachments, avatars and generated images are disabled
Knowledge basesAGENTSET_API_KEYKnowledge bases unavailable; project documents still search locally with pgvector
Background jobsINNGEST_SIGNING_KEY, INNGEST_EVENT_KEYScheduled tasks and the project brain need your own cron — see below
Resumable streamsREDIS_URLA stream ends when the viewer navigates away
Code sandboxE2B_API_KEYGenerated code runs in the in-browser worker only
Web searchEXA_API_KEYThe web search tool is unavailable
Voice transcriptionASSEMBLYAI_API_KEYRealtime voice still works; transcription does not
Browser notificationsNEXT_PUBLIC_VAPID_PUBLIC_KEY, VAPID_PRIVATE_KEYNo notifications while the app is closed
Connected appsCOMPOSIO_API_KEYUsers cannot connect Gmail, Slack, GitHub and other apps
ObservabilitySUPERLOG_PUBLIC_TOKENTraces and logs stay local

Running without Inngest. Scheduled tasks and the sandbox reaper are plain HTTP endpoints. Set SCHEDULED_TASK_SECRET and call them from any cron:

curl -X POST https://your-instance/api/scheduled-tasks/cron \
  -H "X-Scheduled-Task-Auth: $SCHEDULED_TASK_SECRET"

Models

The gateway is the default and covers the whole catalog. You can also:

  • Run models locally. Connect Ollama, LM Studio, or any OpenAI-compatible endpoint from the model picker. Nothing leaves your machine, and it needs no server configuration — each account sets up its own.
  • Use TensorX. EU-hosted inference with zero data retention, reached directly rather than through the gateway. Set TENSORX_API_KEY.
  • Add any OpenAI-compatible provider with OPENAI_COMPATIBLE_DATA: pnpm openai-compatiable:init && pnpm openai-compatiable:parse.

Partners

TensorX — EU-hosted model inference with zero data retention. better-chatbot talks to TensorX directly rather than through a gateway, so prompts go straight to TensorX's EU infrastructure. Create a key at tensorx.ai, set TENSORX_API_KEY, and its models appear in the model picker next to the gateway's. See its trust and security page and DPA.

TensorX is optional. Without the key everything else works as before.


Community

  • Discord — questions, help, and what people are building
  • Issues — bugs and feature requests
  • CONTRIBUTING.md — how to work in this repository

This edition, and the hosted one

better-chatbot is the community edition of keinsaas Navigator. Everything above is here, in full, with no usage caps and no telemetry.

What Navigator adds is what teams need and single users do not: shared team workspaces with member management and invitations, per-member AI budgets and org-wide model policy, billing, a managed workflow builder, and a Slack bot. If you are running this for yourself or a small group, you are not missing anything — that is the point.


License

MIT. See LICENSE.

Originally forked from cgoinglove/better-chatbot, whose work this is built on.

Repozitoriyni ochish ↗