AI Support Bot

Gallery image 1
Gallery image 2
Gallery image 3

RAG-style chat over your own knowledge base, with a full-stack demo and evaluation hooks

This project is a chat UI backed by FastAPI, LangChain, ChromaDB, and an OpenAI-compatible model path, wired for retrieval-augmented answers from custom knowledge you load. The README states responses are scored on dimensions such as relevance, accuracy, coherence, completeness, creativity, tone, and intent alignment: a QA-oriented lens, not a guarantee of correctness.

When it is useful

You are prototyping internal help bots, demoing RAG to stakeholders, or learning how chunking, retrieval, and prompting fit together. Run it with Docker Compose as documented; configure secrets in the backend environment file.

What you can do

  • Load or refresh knowledge sources using the project’s flow so answers stay tied to your material.
  • Chat through the web front end and inspect how the app surfaces answers.
  • Extend storage or logging; the README notes pending work like a durable store for queries and responses.

Limits

  • Wrong or harmful answers remain possible; use human escalation for regulated, safety-critical, or high-stakes topics.
  • Evaluation scores are heuristic; they do not replace human review or compliance sign-off.
  • Cost, retention, and data residency for embeddings and logs are your operational decisions.

Frequently asked questions

What is AI Support Bot?

It is a full-stack RAG chatbot over custom knowledge bases, built with React, FastAPI, LangChain, ChromaDB, and OpenAI. You load knowledge and chat through a web UI.

How do I run it?

Adjust the backend .env if needed, then docker compose up --build. Frontend is at localhost:5173 and backend at localhost:8081.

How are responses evaluated?

The README says the model responses are scored on relevance, accuracy, coherence, completeness, creativity, tone, and intent alignment. Those scores are heuristics, not a guarantee of correctness.

What is still unfinished?

Pending work noted in the README includes adding a SQL or NoSQL store for user queries and generated responses. Wrong answers remain possible; escalate regulated or safety-critical topics to humans.

Continue exploring