botpress
botpress/botpress
Botpress Cloud - The ultimate platform for building next-generation chatbots and assistants powered by OpenAI.
Overview
Repository housing integrations, developer tools, bots, and plugins needed to build GPT/LLM-driven agents and chatbots with Botpress. Maintained and contributed by the Botpress community.
Categories
Tags
Similar tools
ECC
affaan-m/ECC
The agent harness performance optimization system
AutoGPT
Significant-Gravitas/AutoGPT
AutoGPT: Build, Deploy, and Run AI Agents
ollama
ollama/ollama
Get up and running with Kimi-K2.6, GLM-5.1, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.
prompts.chat
f/prompts.chat
The world's largest open-source prompt library for AI
transformers
huggingface/transformers
🤗 Transformers: the model-definition framework for state-of-the-art machine learning models
JavaGuide
Snailclimb/JavaGuide
Snailclimb/JavaGuide: 面试 & 后端通用面试指南,覆盖计算机基础、数据库、分布式、高并发、系统设计与 AI 应用开发
Install
npm install botpressREADME
Botpress Cloud
Botpress is the ultimate platform for building next-generation chatbots and assistants powered by OpenAI. Start building incredible assistants for your projects or businesses at lightning speed.
Getting started • Cloud • Documentation • Integrations • Plugins
This Repository
This repository contains:
- Integrations – all public integrations on the Botpress Hub maintained by Botpress
- Devtools – all Botpress Cloud dev tools (CLI, SDK, API Client)
- Bots - some example of bots "as code" made only using the SDK and the CLI
- Plugins – all plugins on the Botpress Studio (coming soon)
Contributing
We love contributions from the community!
We welcome pull requests and issues relevant for any code contained in this repository. See the This Repository section for more details.
For bugs or features related to Botpress Cloud, you may create an issue on this repository, but keep in mind that you will get a faster response by talking to us on Discord instead!
For any problem related to on-premise Botpress v12, please see the Botpress v12 repository.
Integrations
The /integrations folder contains all our public and open-source integrations. We invite the community to contribute to our integrations or to publish their own to the Botpress Hub.
Integration Development
To develop an integration, start by installing the Botpress CLI:
npm install -g @botpress/cli # for npm
yarn global add @botpress/cli # for yarn
pnpm install -g @botpress/cli # for pnpm
Then, in the directory of your choice, create a new integration:
bp init
This command will generate an integration from one of the proposed templates.
This step can be executed in any directory and git repository of your choice. You don't have to fork this repository to create an integration.
You can then modify both the definition and implementation of your integration respectively located in the integration.definition.ts and src/index.ts files.
For more information on how to develop an integration, please refer to the Documentation.
Integration Deployment
To try out your integration, you can deploy its current version to your workspace using the Botpress CLI:
bp deploy
This will deploy your integration's current version to your workspace and make it available to all your bots. If this version is already deployed, it will be updated. Otherwise, a new version will be created.
By default, all integrations are private to the workspace they have been deployed in. When you are ready to share your version with the community, you can make it public by running:
bp deploy --visibility public
This will make your integration available to all Botpress users on the Botpress Hub. Once a version of your integration is public, it cannot be updated again.
Bots
The /bots folder contains examples of bots "as code" made only using the client, the SDK and the CLI.
This is not the recommended way to build bots and is in no way a replacement for the Botpress Studio.
However it can be useful for experienced developers who want to build bots in a more programmatic way.
It is also used internally by the Botpress team since the Studio and SDK both use the same under