Multi-Bot Telegram Setup

Create a folder per project. Each folder contains the codebase and a CLAUDE.md file with instructions for that specific bot — its personality, knowledge, and rules.

~/Projects/
├── personal-assistant/    # General AI helper
├── project-alpha/         # Project A
├── project-beta/          # Project B
├── project-gamma/         # Project C
└── ...

Each folder has:
├── CLAUDE.md              # Bot instructions & personality
├── src/                   # Project source code
└── knowledge/             # Reference docs (optional)

For each project, open the folder in Claude Code and connect it to a Telegram bot:

# Step 1: Open the project in Claude Code
cd ~/Projects/project-alpha && claude

# Step 2: Configure the Telegram plugin
/telegram:configure
→ Paste the bot token from @BotFather

# Step 3: Set access permissions
/telegram:access
→ Link your Telegram user ID (only you can talk to the bot)

# Config is saved in:
~/.claude/channels/telegram-[name]/access.json

💡 Repeat this for every project/bot combination. Each bot gets its own channel directory.

MCP (Model Context Protocol) servers let your bots reach beyond chat into databases, browsers, queues, file systems, and even each other. Configure them once in ~/.claude/settings.json and every bot inherits them.

// ~/.claude/settings.json
{
  "mcpServers": {
    "supabase": {
      "command": "npx",
      "args": ["-y", "@supabase/mcp-server-supabase@latest",
               "--access-token", "sbp_..."]
    },
    "claude-peers": {
      "command": "bun",
      "args": ["/path/to/claude-peers-mcp/server.ts"]
    },
    "playwright": {
      "command": "npx",
      "args": ["@playwright/mcp@latest"]
    }
  }
}

💡 claude-peers turns your machine into a peer network: each bot can list, message, and delegate work to other bots running on the same machine. A specialist bot can hand a task to a generalist coordinator and vice versa, without you in the loop.

This is the magic — one script that starts all your bots in separate tmux windows. Create it at ~/.claude/scripts/start-all-sessions.sh

#!/bin/bash
# Start all Claude Code bot sessions
# Usage: ~/.claude/scripts/start-all-sessions.sh

SESSIONS=(
  "assistant|~/Projects/personal-assistant|telegram-assistant"
  "alpha|~/Projects/project-alpha|telegram-alpha"
  "beta|~/Projects/project-beta|telegram-beta"
  "gamma|~/Projects/project-gamma|telegram-gamma"
)

for session_info in "${SESSIONS[@]}"; do
  IFS='|' read -r name folder channel <<< "$session_info"

  # Skip if already running
  if tmux has-session -t "$name" 2>/dev/null; then
    echo "Already running: $name"
    continue
  fi

  # Start Claude Code in a new tmux session
  tmux new-session -d -s "$name" -c "$folder" \
    "TELEGRAM_STATE_DIR=~/.claude/channels/$channel \
     claude --channels 'plugin:telegram@claude-plugins-official' \
     --dangerously-skip-permissions"

  echo "Started: $name → $folder"
  sleep 2  # Prevent resource spikes
done

echo "All sessions started!"

💡 Make it executable: chmod +x ~/.claude/scripts/start-all-sessions.sh

After a reboot or restart, run one command to bring up all your bots:

~/.claude/scripts/start-all-sessions.sh

# Output:
Started: assistant → ~/Projects/personal-assistant
Started: alpha → ~/Projects/project-alpha
Started: beta → ~/Projects/project-beta
Started: gamma → ~/Projects/project-gamma
All sessions started!

💡 That's it. All bots are now running and listening to their Telegram channels. You can message any bot from your phone.

Useful commands for managing your bot sessions:

# See all running sessions
tmux list-sessions

# Attach to a session (watch what the bot is doing)
tmux attach -t alpha

# Detach from a session (keep it running)
Ctrl+B then D

# Kill a single session
tmux kill-session -t alpha

# Kill all sessions
tmux kill-server

# Restart everything
~/.claude/scripts/start-all-sessions.sh