switchroom weekly downloads statistics

<p align="center"> <img src="docs/assets/switchroom-hero-wide.png" alt="Switchroom: a standing team of specialist assistants on your Claude Pro or Max subscription, run from Telegram" width="100%"> </p>

Switchroom

A switchboard for your Pro or Max. Your standing team. Specialist assistants who remember you, own their patch, and act, while you get on with life. You text them from Telegram. They run on the Claude subscription you already pay for.

Latest release notes →

Why this exists

I loved OpenClaw + Telegram. I wanted my Claude subscription. And the UX done properly. So I built this.

The use case came from OpenClaw: always-on assistants in a chat app, each with a personality and a job. Good idea. Three things stopped it being the one I needed, and nothing else fixed them:

• On the subscription, properly. The Claude plan I already pay for, the same OAuth as the desktop. Compliant. Predictable cost. Not an API meter. Not a second invoice.
• On the leash. Give an assistant broad standing access and one day it helpfully does something irreversible. Credentials, tools, skills: granted deliberately, approved by a human, no way around it.
• Telegram, done properly. Not a bridge spread thin across Slack, Discord, Teams. One channel. Opinionated. Excellent.

So I built it.

See it work

You text a specialist the way you'd text a good assistant. Here is clerk, a chief of staff that runs the calendar, watches the health data, and fields the household asks, all in one voice, because it knows you across all of it.

You: move my 3pm to Thursday and tell Sarah why

clerk knows your week and knows who Sarah is. It gets on with it, then tells you in plain words what it did. No tool-call log to babysit.

clerk
Thursday 3 to 4pm is clear. Moved "Design review" there.

Drafted a note to Sarah:
  "Had to shift our 3pm to Thursday. Same agenda,
   see you then."

Send it?                          [ Send ]   [ Edit ]

It does the work itself. It stops at the one thing that matters, the message leaving your hands, and waits for your tap. Nothing with consequences happens on the agent's say-so alone. You are never left wondering what it is doing, and you never have to watch it. Full UX behaviour →

Quickstart

Runs on the box you already have. Supported production runtime is Linux + Docker. Canonical target: Ubuntu 24.04 LTS, 4 GiB RAM minimum, 8 GiB once you run more than one agent. macOS (Docker Desktop) works for development, not yet release-validated.

Fresh Linux box, one script:

curl -fsSL https://github.com/switchroom/switchroom/raw/main/scripts/install-deps.sh | sudo bash

Installs Docker Engine + Compose v2, Node.js 20.11+, Bun, and the @anthropic-ai/claude-code + switchroom CLIs. Idempotent. Log out and back in so the docker group takes effect, then:

switchroom setup                       # interactive: Telegram + vault + first agent
switchroom apply                       # generate ~/.switchroom/compose/docker-compose.yml
docker compose -p switchroom -f ~/.switchroom/compose/docker-compose.yml up -d
switchroom auth add default --via-claude   # OAuth your Pro/Max account, AFTER the fleet is up
switchroom auth use default                # make it the fleet-wide active account

Auth comes after the fleet is up on purpose. The switchroom-auth-broker is the sole writer of credentials and does not exist until the compose stack is running. After this you talk to the agent from Telegram and never touch the server again. To catch a running host up later use switchroom update, not a raw docker compose up (a bare compose-up on a live fleet skips the operator restart-marker, so boot cards render as crashes).

Already in Claude Code? Shortest path. Inside any session:

/plugin marketplace add switchroom/switchroom
/plugin install switchroom@switchroom
/switchroom:setup

Full new-user walkthrough, zero to first Telegram message in ~15 minutes, plus the npm-only path, the no-wizard one-shot, the BotFather steps, and static-binary status: docs/install.md.

What you get…