claude-code-mux 0.1.0 → 0.1.2

package/README.md

@@ -1,41 +1,55 @@
-# claude-mux
+# claude-code-mux
 
-One messaging client, many Claude Code agents. A multiplexer that routes messages between a messaging platform (Telegram, Discord, etc.) and multiple Claude Code sessions running on different worktrees.
+Talk to all your Claude Code agents from your phone. From a single mobile messaging app, chat with them in their active session, switch between agents, get notified when tasks finish, and approve permissions on the go. Seamlessly pick up where you left off — start a task on your desktop, continue the conversation from your phone.
 
-<img src="demo.png" width="400" alt="claude-mux demo — Telegram chat showing /list, /status, /help commands and agent switching" />
 
-## Architecture
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `/list` | Show all connected agents |
+| `/switch <agent>` | Switch to an agent by repo, branch, directory, or description |
+| `/status` | Show which agent is active |
+| `/help` | Show all commands |
+| *(any message)* | Chat with the active agent, just like in the terminal |
+
+## Usage (from Telegram)
 
 ```
-Telegram Bot
-    |
-    v
-Router (standalone process, localhost:9900)
-  - Owns the bot token
-  - Handles /list, /switch, /status commands
-  - Fuzzy-matches agent names on /switch
-  - Natural language switching via LLM (Anthropic, OpenAI, or Google)
-  - Routes messages to the active agent
-    |  (WebSocket)
-    v
-Bridge (MCP channel plugin, one per Claude Code session)
-  - Auto-detects agent name from git (repo/branch)
-  - Registers with router on startup
-  - Pushes messages into Claude Code session
-  - Sends replies + notifications back through router
+You: /switch nav
+Bot: Switched to myapp/feature-nav
+
+You: switch to the one working on the bug fix
+Bot: Switched to myapp/fix-auth-bug
+
+You: can you add pagination to the /users endpoint?
+Bot: [monots/encore] I'll add pagination to the /users endpoint...
+
+Bot: [myapp/feature-nav] Finished refactoring the nav component.
+     Changed 3 files, all 24 tests passing.
+     Ready for your review.
+
+Bot: [monots/encore] Permission request:
+     Tool: Bash — Run npm test
+     Reply "yes abcde" or "no abcde"
+You: yes abcde
 ```
 
 ## Install
 
 ```bash
-npm install -g claude-mux
+npm install -g claude-code-mux
 ```
 
 ## Prerequisites
 
 - Claude Code v2.1.80+
 - Node.js 20+
-- A Telegram bot token (see [Create a Telegram Bot](#create-a-telegram-bot) below)
+- A messaging platform bot token:
+  - **Telegram** — supported now (see [Create a Telegram Bot](#create-a-telegram-bot) below)
+  - **Discord** — coming soon
+  - **WhatsApp** — coming soon
+  - **Slack** — coming soon
 
 ## Create a Telegram Bot
 
@@ -137,81 +151,6 @@ claude --dangerously-load-development-channels server:claude-mux-bridge
 
 No per-session env vars needed. Each session registers with the router automatically. When you spin up a new worktree, just start Claude Code in it — no extra setup required.
 
-## Usage (from Telegram)
-
-### Commands
-
-| Command | Description |
-|---------|-------------|
-| `/list` | Show all connected agents |
-| `/switch <agent>` | Switch to an agent by repo, branch, directory, or description |
-| `/status` | Show which agent is active |
-| `/help` | Show all commands |
-
-### Smart switching
-
-You don't need to type the exact agent name. The router first tries token-based fuzzy matching (instant, no API call). If that's ambiguous, and you've configured a `ROUTER_MODEL`, it falls back to the LLM to interpret natural language:
-
-```
-You: /list
-Bot: Connected agents:
-       monots/encore (active) — up 32m
-       myapp/feature-nav — up 15m
-       myapp/fix-auth-bug — up 5m
-
-You: /switch monots encore
-Bot: Switched to monots/encore
-
-You: /switch nav
-Bot: Switched to myapp/feature-nav
-
-You: /switch myapp
-Bot: Multiple matches for "myapp":
-       1. myapp/feature-nav
-       2. myapp/fix-auth-bug
-     Be more specific, or use /switch with the full name.
-
-You: /switch fix auth
-Bot: Switched to myapp/fix-auth-bug
-
-You: switch to the one working on the bug fix
-Bot: Switched to myapp/fix-auth-bug
-```
-
-The last example doesn't use a `/` command at all. Any message containing the word "switch" triggers the LLM to classify whether it's a switch intent or a regular message to the agent. This means "switch to the one working on the bug fix" gets intercepted and resolved by the LLM, while "can you switch the database driver to postgres" passes through to the agent as a normal message. Without a `ROUTER_MODEL` configured, only `/switch` commands with fuzzy matching are available.
-
-### Chatting with agents
-
-Any non-command message goes to the active agent. If only one agent is connected, it's auto-selected.
-
-```
-You: can you add pagination to the /users endpoint?
-Bot: [monots/encore] I'll add pagination to the /users endpoint...
-```
-
-### Notifications
-
-Agents proactively notify you when tasks complete:
-
-```
-Bot: [myapp/feature-nav] Finished refactoring the nav component.
-     Changed 3 files, all 24 tests passing.
-     Ready for your review.
-```
-
-### Permission relay
-
-When an agent needs permission to run a tool, you'll get a prompt:
-
-```
-Bot: [monots/encore] Permission request:
-     Tool: Bash
-     Action: Run npm test
-     Reply "yes abcde" or "no abcde"
-
-You: yes abcde
-```
-
 ## Dynamic worktrees
 
 The whole point of this tool: you don't create new bots or set env vars when you spin up a new worktree. Just start Claude Code in the directory:
@@ -223,6 +162,22 @@ claude --dangerously-load-development-channels server:claude-mux-bridge
 
 The bridge detects `myapp/hotfix-123` from git and registers automatically. When you close the session, it deregisters and your Telegram shows a disconnect notification.
 
+## Architecture
+
+```
+Telegram Bot
+    |
+    v
+Router (standalone process, localhost:9900)
+  - Handles /list, /switch, /status commands
+  - Routes messages to the active agent
+    |  (WebSocket)
+    v
+Bridge (MCP channel plugin, one per Claude Code session)
+  - Pushes messages into Claude Code session
+  - Sends replies + notifications back through router
+```
+
 ## Configuration
 
 ### Router

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-mux",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "One messaging client, many Claude Code agents — a multiplexer for routing messages to multiple Claude Code sessions",
   "type": "module",
   "bin": {
@@ -8,8 +8,7 @@
     "claude-mux-bridge": "./dist/bridge.js"
   },
   "files": [
-    "dist",
-    "demo.png"
+    "dist"
   ],
   "scripts": {
     "build": "tsc",
@@ -25,6 +24,14 @@
     "multiplexer",
     "agent"
   ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/ShiplightAI/claude-code-mux.git"
+  },
+  "homepage": "https://github.com/ShiplightAI/claude-code-mux#readme",
+  "bugs": {
+    "url": "https://github.com/ShiplightAI/claude-code-mux/issues"
+  },
   "license": "MIT",
   "dependencies": {
     "@ai-sdk/anthropic": "^3.0.63",