Can I vibecode MagicChat?

KINDA · weekend project

price $58/moyou'd save $696/yrbuild time weekendcategory 🛟 customer supportreplaced by 0 people

A retrieval chatbot over your own docs is one of the most one-shottable products there is: crawl the site, chunk and embed it, answer from the top matches with an LLM, drop in a widget. What you don't get for free is the boring operational layer, scheduled re-crawls, analytics, lead capture and human handoff, multi-source connectors, and a hosted widget that stays up. Buildable in a weekend, real gaps after that.

the prompt

Build me an AI support chatbot that trains on my own website and docs, to replace
MagicChat, in an empty repo.

Stack (no alternatives): Next.js 15 (App Router) + TypeScript, Postgres with the
pgvector extension via Drizzle ORM, and Docker Compose so `docker compose up` runs
Postgres and the app together. Use the OpenAI or Anthropic API for both embeddings
and answers (keys in .env).

Core loop:
- `npm run ingest -- <sitemap-or-url>`: crawl the pages, strip to clean text, chunk
  (~800 tokens with overlap), embed each chunk, and store text + vector + source URL
  in Postgres.
- A /api/chat route: embed the incoming question, pull the top-k chunks by cosine
  similarity, and ask the LLM to answer ONLY from that context, returning the source
  URLs it used. Stream the answer.
- A single embeddable widget: one <script> tag mounts a floating chat bubble on any
  site, talking to /api/chat with CORS locked to configured origins.

Details:
- One config file: bot name, greeting, allowed origins, model, top-k.
- Store everything locally in Postgres; `npm run reindex` re-crawls and replaces.
- Secrets in .env, ship .env.example, never commit keys.
- Handle empty, loading, and "I don't know from the docs" states honestly; never
  invent answers outside the retrieved context.
- Out of scope: multi-channel (email/WhatsApp/Slack), team seats, an analytics
  dashboard, human handoff, scheduled auto-refresh (leave a documented cron hook),
  and any hosted control plane.
- README: setup, the ingest command, embedding the widget, and where data lives.

$ open in your agent (prompt prefilled, you press enter) or copy it raw

why people still pay

People pay so they never touch the plumbing: the crawler that re-indexes when docs change, the dashboard that shows what customers asked, the connectors to their help desk, and a widget that stays up without them running a server. The RAG is easy; keeping it fresh, measured and online is the recurring work.

what you lose

xscheduled auto re-crawl and content refresh

xanalytics and conversation-history dashboards

xlead capture and human handoff

xmulti-source connectors and integrations

xhosted uptime for the widget

xteam seats and enterprise compliance (HIPAA/DPA/BAA)

share on X ↗"I just replaced MagicChat ($58/mo) with one prompt"

the escape hatch

Don't feel like building it? These folks already made it free.

OnyxSelf-hosted chat over your own docs with connectors and permissions; heavier to run than a widget, but the whole RAG loop is yours.32kaug 2026open source↗

no votes, no pay-to-list · just what's real