Dm Other Claudes

dm-other-claudes

Let your main Claude Code instance communicate with remote Claude Code instances over SSH. Instead of copying messages back and forth between terminal windows, your Claudes can just talk to each other directly.

Born from the annoyance of manually relaying messages between Claude Code sessions on different servers. Each Claude knows its own machine best — now they can collaborate without you playing telephone.

This is just how my system is set up. Feel free to fork, improve, and personalize it for yourself.

┌─────────────────┐         SSH + stdin          ┌─────────────────┐
│  Claude Code    │ ──────────────────────────>  │  Claude Code    │
│  (interactive)  │                              │  (headless)     │
│  your laptop    │  <────────────────────────── │  remote server   │
│                 │     JSON response + session   │                 │
└─────────────────┘                              └─────────────────┘

Your local Claude sends a prompt to a remote machine via SSH, where another Claude Code instance runs it headlessly (`claude -p`), and the response comes back. Sessions are tracked so you can have multi-turn conversations across machines.

Prerequisites

• Bun installed on your local machine
• Claude Code CLI installed and authenticated on both local and remote machines
• SSH key-based auth to the remote machine(s)

Installation

1. Copy the skill files

mkdir -p ~/.claude/skills/dm-other-claudes
cp dm-claude.ts SKILL.md ~/.claude/skills/dm-other-claudes/

2. Tell Claude how to use it

Add something like this to your `CLAUDE.md` (either `~/.claude/CLAUDE.md` for global, or a project-level one):

### Cross-Claude Communication (dm-claude)

I can send tasks to Claude Code instances on remote machines using the dm-claude tool.

**Tool location**: `bun run ~/.claude/skills/dm-other-claudes/dm-claude.ts`

**My remote ag