BotServer banner
LoopyLuci LoopyLuci

BotServer

Design community

Description

Telegram/Discord/Slack bot that drives Claude through Anthropic API, Claude Code CLI, or Claude Desktop UI automation, controlled from a Tauri desktop dashboard as well as Hermes Agent connections and bot control

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Bot Server

Run any number of independent bots at once — a Claude bot and a separate Hermes Agent bot, each on Telegram, Discord, and/or Slack, all simultaneously, each with its own fully separate chat history and job queue. Every bot routes through one of five interchangeable backends (Anthropic API, Claude Code CLI, best-effort UI automation of Claude Desktop, or Hermes Agent via its CLI or its JSON-RPC gateway), and any group of bots can be wired together into a **swarm** — a named group that collaborates on one prompt via a pluggable strategy (parallel fan-out with a synthesizer, a leader picking the best answer, a sequential draft-then-refine pipeline, planner/worker task decomposition, or a fully custom step graph). Everything — starting bots, watching them boot, and controlling them afterward — happens inside one desktop app; there's no separate script-then-browser step.

Companion design docs (published earlier in this project's chat): architecture spec and dashboard mockup. This repo is the working implementation of both, plus the desktop shell.

Beyond routing prompts to bots, the app also ships a **Support Bot** — a small, fully local, dependency-free AI model built into the desktop app that understands plain-English server-management requests ("restart Claude Desktop", "what's my default backend") and every slash command, so you can manage the whole server from one chat panel without touching config files. There's also a companion **Android app** with feature parity for chat, bot management, and the Support Bot from your phone.

Dashboard tour

The desktop app's sidebar has one tab per system. Everything below is covered in depth further down this README (or in its own linked doc) — this is just the map:

Tab What it's for
Overview KPIs at a glance: job counts, desktop process state, DB size, config version, default backend.
Jobs Every /ask attempt, filterable by status, with a completed/failed timeseries and per-