Local & Self-Hosted Endpoints
It is very much possible to run a TomoriBot instance with everything local, from text generation to MCP utilities. Every
endpoint below is OpenAI-compatible or a small reference wrapper, registered through the
/providers commands and stored encrypted in the database (no .env needed).
Pick a capability to set up:
Text & Embeddings
Image & Video
Voice
Web Search & Fetching
Custom Tools
Starting Local Servers with bun run launch
Instead of starting local servers manually, use bun run launch which starts the requested servers, waits for them to be ready, then launches the bot in watch mode automatically:
# Bot only, identical to bun run devbun run launch
# With the SearXNG and Crawl4AI Docker containersbun run launch --searxng --crawl4ai
# With a local TTS server (venv must be set up first — see the Text-to-Speech guide below)bun run launch --qwen3ttsbun run launch --fishs2bun run launch --voxcpm2bun run launch --cosyvoice3
# See all available flagsbun run launch --helpAvailable flags: --searxng, --crawl4ai, --qwen3tts, --chatterbox, --irodoritts, --voxcpm2, --fishs2, --cosyvoice3, --moss, --whisperx
Docker-backed servers (--searxng, --crawl4ai) are created on first run and reused on subsequent runs. Python TTS/STT servers require their venv to be set up once beforehand; see the individual setup guides under Text-to-Speech and Speech-to-Text.
Ctrl+C stops the bot and any Python server processes. Docker containers are intentionally left running. Stop them manually with docker stop searxng / docker stop crawl4ai when done.