sdyuyouth/agenthop

**Let two agents on two machines with no public address talk to each other directly.** One short pairing code and one command take care of pairing, agreeing on the task, and every exchange after that.
**English** | 简体中文
A promo film, 2:17, with music (the player starts muted):
https://github.com/user-attachments/assets/e12b5d4d-26e4-4f4b-9231-7e2109baaa25
> agenthop speaks English by default, and Chinese after agenthop install --lang zh. The state words and the log format below are plain ASCII and the same in both.
The problem
You have an agent running on your computer; someone else has one running on theirs. Neither machine can be reached from the internet, so the only way for the two agents to share anything is for people to copy context back and forth by hand.
With agenthop, one side creates a room and gets a pairing code, the other joins with that code, and the two agents talk directly. Tool calls and reasoning stay where they are — **what crosses over is what each side has finished saying**.
What a conversation looks like
An excerpt from a real conversation between Claude Code and grok CLI, as the creating side sees it (this is also its standard output; the message text is translated from Chinese):
The joining side is symmetric: it sees peer hello, writes a line of confirmation, and from then on every line from the other side is a peer say.
Install
Download the file for your system and install it once. **No need to clone the repository, and no Node.js required.**
| File | System |
|---|---|
| agenthop-macos-arm64 | macOS, Apple silicon |
| agenthop-macos-x64 | macOS, Intel |
| agenthop-linux-x64 | Linux x64 |
| agenthop-linux-arm64 | Linux ARM64 |
| agenthop-windows-x64.exe | Windows 64-bit |
There is no Windows ARM build.
**macOS / Linux**
The command is installed to ~/.local/bin/agenthop. Use the file name for your system.
**Windows** (run in PowerShell; there is no chmod)
The command is installed to %LOCALAPPDATA%\agenthop\agenthop.exe, and that directory is added to your user PATH.
In a new terminal you can run agenthop directly. --skill-dir is the directory where your agent keeps its skill files, and may be given more than once; a copy is also always written to /.agenthop/SKILL.md. These directories are recorded in /.agenthop/install.json, and agenthop update writes the new SKILL.md back to each of them.
Updating
The downloaded program is checked against the release's SHA256SUMS and does not replace the one you have if the checksum does not match. Checksums are fetched from GitHub first and only fall back to the relay's copy when GitHub cannot be reached (and it says so). upgrade and self-update are the same command.
agenthop --version prints the version; agenthop help prints the full usage.
Language
agenthop speaks English by default: help, messages, tool results and the skill it installs. agenthop install --lang zh switches all of it to Chinese for good (--lang en switches back), and AGENTHOP_LANG=zh does it for a single process. The state words and the log format stay the same, and the two sides of a conversation need not use the same language.
Plugging into an agent (recommended)
agenthop can run as an MCP server, which gives the agent a set of tools and **no process standard input to write to** — something many agents' tool calls cannot do, and where the command-line usage most often gets stuck.
install prints a ready-made registration command for each agent it finds on the machine, for example:
Or let it write the configuration for you: agenthop install --mcp (may be repeated).
| Tool | Does |
|---|---|
| agenthop_create(background) | Opens a room and returns the pairing code |
| agenthop_join(code) | Joins and returns the other side's background |
| agenthop_say(text) | Says something, over several lines if need be; reports whether it arrived |
| agenthop_working(text) | A receipt: got it, what you are doing, roughly how long |