🦞 ClaudeClaw v2
A multi-channel bridge for Claude Code. Run one persistent agent per chat
(Telegram / Discord / Slack / LINE), backed by real claude CLI sessions
inside tmux — so every Claude Code feature (skills, hooks, plugins, MCP,
slash commands) is available out of the box.
┌─ Telegram ─┐
│ Discord │──► Channel Daemon (Bun/TS) ──► per-channel tmux session
│ Slack │ • routes I/O running `claude --resume`
│ LINE │ • tails jsonl writes to your project
└─ Web API ──┘ • cron + heartbeat and ~/.claude/projects/
Why v2
v1 wrapped the Claude Agent SDK and re-implemented features Claude Code
already has. v2 runs Claude Code as-is inside tmux and just plays
post-office:
- All Claude Code features come for free (skills, hooks, plugins, MCP)
- Per-channel state is durable via the CLI's own session jsonl
- Cross-session messaging is plain files in
.claude/claudeclaw/inbox/
- Restart is safe: tmux outlives the daemon, context never lost
- Smaller surface, fewer abstractions to maintain
Design background and spike findings live in docs/redesign.md.
Features
- Platforms: Telegram (long-poll), Discord (Gateway WS), Slack (Socket
Mode), LINE (webhook) — all with text, media download, and reactions
- Cross-platform DM sink: Telegram + Discord/Slack/LINE DMs all share
one "global" session, just like v1
- Per-channel sessions: each Discord channel, Slack thread, LINE group
gets its own
claude --session-id so context never bleeds across
- Cron:
.md files with frontmatter (schedule, target, replyTo) —
agent can manage them itself via Write/Read
- Heartbeat: periodic ambient prompt with quiet-hours support
- Model routing: per-turn
/model switch based on keyword classifier
(planning → opus, implementation → sonnet, etc.)
- Reactions: agent emits
[react:🌸] in its reply, daemon strips and
applies as a native platform reaction
- Web dashboard: status, transcripts, jobs, logs (
http://127.0.0.1:4632)
- HTTP API:
/api/send, /api/trigger for cross-session messaging
- CLI:
bun run src/cli.ts {status,send,trigger,stop,init}
Quick start
Prerequisites: bun, tmux,
and the Claude Code CLI on your PATH.
Option A — Claude Code plugin (recommended)
Install the repo as a Claude Code plugin, then use the agent-guided
setup wizard:
git clone https://github.com/hans00/claudeclaw2.git \
~/.claude/plugins/marketplaces/claudeclaw2
cd ~/.claude/plugins/marketplaces/claudeclaw2 && bun install
In any Claude Code session, cd into the project directory you want
to use as ClaudeClaw's working dir, then:
/claudeclaw2:init # interactive setup — picks platforms, edits
# settings.json + CLAUDE.md + prompts/ for you
/claudeclaw2:start # boots the daemon
/claudeclaw2:status # health check
All available commands: /claudeclaw2:init, start, stop, status,
sessions, send, trigger, logs, migrate, help.
Option B — Manual
# 1. Clone + install
git clone https://github.com/hans00/claudeclaw2.git ~/Projects/claudeclaw2
cd ~/Projects/claudeclaw2
bun install
# 2. Initialize a project directory
mkdir -p ~/my-project && cd ~/my-project
bun run ~/Projects/claudeclaw2/src/cli.ts init
# 3. Fill in tokens
$EDITOR .claude/claudeclaw/settings.json
$EDITOR CLAUDE.md prompts/*.md
# 4. Start
./start.sh
# logs at .claude/claudeclaw/logs/daemon.log
# web dashboard at http://127.0.0.1:4632
Migrating from v1
If you already run v1 ClaudeClaw, see docs/MIGRATE.md.
The short version:
# stop v1
kill -TERM $(cat .claude/claudeclaw/daemon.pid)
# point your start.sh at v2's daemon
sed -i 's#.*plugins/marketplaces/claudeclaw/src/index.ts.*#nohup bun run ~/Projects/claudeclaw2/src/daemon.ts \\\n > .claude/claudeclaw/logs/daemon.log 2>\&1 \&#' start.sh
# start — v2 auto-migrates v1 state on first boot
./start.sh
First boot reads v1's session.json + sessions.json.threads.* and
rewrites .claude/claudeclaw/sessions.json in v2 shape. The originals
are renamed to *.v1-backup rather than deleted.
Docs
Layout
