Practical overview
When it fits
Use Chibi when a Telegram-based interface and self-hosted control are useful for coordinating models, tools and longer-running agent work. It is also relevant when provider flexibility or MCP connectivity matters more than a single-model chat interface.
Who it is for
- Developers building a self-hosted Telegram AI assistant
- Operators who need one interface for multiple configured model providers
- Teams exploring MCP-connected tools and delegated agent workflows
- Users who want asynchronous research, content or operational tasks
Documented uses
- Route requests across configured AI providers
- Run longer tasks asynchronously
- Delegate work to specialized sub-agents
- Connect external tools through MCP
- Generate supported image, voice or music outputs through configured providers
Requirements & limits
The repository documents pip and Docker setup. A Telegram bot token and at least one configured provider API key are required by the shown setup examples. The project is MIT licensed.
- Telegram is the primary interaction surface, with documented local client frontends available through a JSONL protocol.
- Provider choice is broad, but actual model access depends on configured keys and enabled features.
- MCP, filesystem and terminal connections make tool orchestration a central part of the project.
- Docker and self-hosting are documented deployment contexts.
- The project supports asynchronous work and sub-agent delegation rather than only synchronous chat.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and start Chibi with pip
Set up the Chibi command-line application and start its Telegram bot.
Before you start
- Python package installation through pip
- A Telegram bot token
- At least one AI-provider API key
Steps
Install the package with pip install chibi-bot.
Run chibi config to add API keys and update settings.
Run chibi start to start the bot as a background service.
Expected outcome
Chibi starts as a background service after configuration.
Guide limitations
- The documented steps do not specify provider-specific configuration fields or model selection details.
- The guide does not establish successful execution or compatibility in a particular environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- s-nagaev/chibi · Official homepage title · retained in its source language

