base on AI chat for any model. # Chatbot UI The open-source AI chat app for everyone. <img src="./public/readme/screenshot.png" alt="Chatbot UI" width="600"> ## Demo View the latest demo [here](https://x.com/mckaywrigley/status/1738273242283151777?s=20). ## Updates Hey everyone! I've heard your feedback and am working hard on a big update. Things like simpler deployment, better backend compatibility, and improved mobile layouts are on their way. Be back soon. -- Mckay ## Official Hosted Version Use Chatbot UI without having to host it yourself! Find the official hosted version of Chatbot UI [here](https://chatbotui.com). ## Sponsor If you find Chatbot UI useful, please consider [sponsoring](https://github.com/sponsors/mckaywrigley) me to support my open-source work :) ## Issues We restrict "Issues" to actual issues related to the codebase. We're getting excessive amounts of issues that amount to things like feature requests, cloud provider issues, etc. If you are having issues with things like setup, please refer to the "Help" section in the "Discussions" tab above. Issues unrelated to the codebase will likely be closed immediately. ## Discussions We highly encourage you to participate in the "Discussions" tab above! Discussions are a great place to ask questions, share ideas, and get help. Odds are if you have a question, someone else has the same question. ## Legacy Code Chatbot UI was recently updated to its 2.0 version. The code for 1.0 can be found on the `legacy` branch. ## Updating In your terminal at the root of your local Chatbot UI repository, run: ```bash npm run update ``` If you run a hosted instance you'll also need to run: ```bash npm run db-push ``` to apply the latest migrations to your live database. ## Local Quickstart Follow these steps to get your own Chatbot UI instance running locally. You can watch the full video tutorial [here](https://www.youtube.com/watch?v=9Qq3-7-HNgw). ### 1. Clone the Repo ```bash git clone https://github.com/mckaywrigley/chatbot-ui.git ``` ### 2. Install Dependencies Open a terminal in the root directory of your local Chatbot UI repository and run: ```bash npm install ``` ### 3. Install Supabase & Run Locally #### Why Supabase? Previously, we used local browser storage to store data. However, this was not a good solution for a few reasons: - Security issues - Limited storage - Limits multi-modal use cases We now use Supabase because it's easy to use, it's open-source, it's Postgres, and it has a free tier for hosted instances. We will support other providers in the future to give you more options. #### 1. Install Docker You will need to install Docker to run Supabase locally. You can download it [here](https://docs.docker.com/get-docker) for free. #### 2. Install Supabase CLI **MacOS/Linux** ```bash brew install supabase/tap/supabase ``` **Windows** ```bash scoop bucket add supabase https://github.com/supabase/scoop-bucket.git scoop install supabase ``` #### 3. Start Supabase In your terminal at the root of your local Chatbot UI repository, run: ```bash supabase start ``` ### 4. Fill in Secrets #### 1. Environment Variables In your terminal at the root of your local Chatbot UI repository, run: ```bash cp .env.local.example .env.local ``` Get the required values by running: ```bash supabase status ``` Note: Use `API URL` from `supabase status` for `NEXT_PUBLIC_SUPABASE_URL` Now go to your `.env.local` file and fill in the values. If the environment variable is set, it will disable the input in the user settings. #### 2. SQL Setup In the 1st migration file `supabase/migrations/20240108234540_setup.sql` you will need to replace 2 values with the values you got above: - `project_url` (line 53): `http://supabase_kong_chatbotui:8000` (default) can remain unchanged if you don't change your `project_id` in the `config.toml` file - `service_role_key` (line 54): You got this value from running `supabase status` This prevents issues with storage files not being deleted properly. ### 5. Install Ollama (optional for local models) Follow the instructions [here](https://github.com/jmorganca/ollama#macos). ### 6. Run app locally In your terminal at the root of your local Chatbot UI repository, run: ```bash npm run chat ``` Your local instance of Chatbot UI should now be running at [http://localhost:3000](http://localhost:3000). Be sure to use a compatible node version (i.e. v18). You can view your backend GUI at [http://localhost:54323/project/default/editor](http://localhost:54323/project/default/editor). ## Hosted Quickstart Follow these steps to get your own Chatbot UI instance running in the cloud. Video tutorial coming soon. ### 1. Follow Local Quickstart Repeat steps 1-4 in "Local Quickstart" above. You will want separate repositories for your local and hosted instances. Create a new repository for your hosted instance of Chatbot UI on GitHub and push your code to it. ### 2. Setup Backend with Supabase #### 1. Create a new project Go to [Supabase](https://supabase.com/) and create a new project. #### 2. Get Project Values Once you are in the project dashboard, click on the "Project Settings" icon tab on the far bottom left. Here you will get the values for the following environment variables: - `Project Ref`: Found in "General settings" as "Reference ID" - `Project ID`: Found in the URL of your project dashboard (Ex: https://supabase.com/dashboard/project/<YOUR_PROJECT_ID>/settings/general) While still in "Settings" click on the "API" text tab on the left. Here you will get the values for the following environment variables: - `Project URL`: Found in "API Settings" as "Project URL" - `Anon key`: Found in "Project API keys" as "anon public" - `Service role key`: Found in "Project API keys" as "service_role" (Reminder: Treat this like a password!) #### 3. Configure Auth Next, click on the "Authentication" icon tab on the far left. In the text tabs, click on "Providers" and make sure "Email" is enabled. We recommend turning off "Confirm email" for your own personal instance. #### 4. Connect to Hosted DB Open up your repository for your hosted instance of Chatbot UI. In the 1st migration file `supabase/migrations/20240108234540_setup.sql` you will need to replace 2 values with the values you got above: - `project_url` (line 53): Use the `Project URL` value from above - `service_role_key` (line 54): Use the `Service role key` value from above Now, open a terminal in the root directory of your local Chatbot UI repository. We will execute a few commands here. Login to Supabase by running: ```bash supabase login ``` Next, link your project by running the following command with the "Project ID" you got above: ```bash supabase link --project-ref <project-id> ``` Your project should now be linked. Finally, push your database to Supabase by running: ```bash supabase db push ``` Your hosted database should now be set up! ### 3. Setup Frontend with Vercel Go to [Vercel](https://vercel.com/) and create a new project. In the setup page, import your GitHub repository for your hosted instance of Chatbot UI. Within the project Settings, in the "Build & Development Settings" section, switch Framework Preset to "Next.js". In environment variables, add the following from the values you got above: - `NEXT_PUBLIC_SUPABASE_URL` - `NEXT_PUBLIC_SUPABASE_ANON_KEY` - `SUPABASE_SERVICE_ROLE_KEY` - `NEXT_PUBLIC_OLLAMA_URL` (only needed when using local Ollama models; default: `http://localhost:11434`) You can also add API keys as environment variables. - `OPENAI_API_KEY` - `AZURE_OPENAI_API_KEY` - `AZURE_OPENAI_ENDPOINT` - `AZURE_GPT_45_VISION_NAME` For the full list of environment variables, refer to the '.env.local.example' file. If the environment variables are set for API keys, it will disable the input in the user settings. Click "Deploy" and wait for your frontend to deploy. Once deployed, you should be able to use your hosted instance of Chatbot UI via the URL Vercel gives you. ## Contributing We are working on a guide for contributing. ## Contact Message Mckay on [Twitter/X](https://twitter.com/mckaywrigley) ", Assign "at most 3 tags" to the expected json: {"id":"1768","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"