Homing Pigeon — Communication skill for Claude Code

Homing Pigeon

Your cloud SI is smart, but it can't touch your computer. Homing Pigeon fixes that: tell your SI to send a signed job, it executes on your machine (Linux/macOS/FreeBSD/Windows), and the results come back so your SI can iterate — run the tests, read the failure, fix, repeat. From your phone, from anywhere.

Think "GitHub self-hosted runner, but the control plane is email." Python 3.9+, standard library only, no dependencies. (Email is just the first transport — the protocol doesn't care about the pipe. See TRANSPORTS.md.)

⚠️ **USE AT YOUR OWN RISK.** This tool hands **full administrative control** of the machine to whoever holds the shared secret. It reads email and executes what it finds — blindly, as a privileged user. Anyone who can produce a correctly-signed email owns the box: install software, read files, add users, pivot to your network. Only run this with a dedicated throwaway account on a machine you can afford to lose, and read PROTOCOL.md before you deploy it.

What this is for

Homing Pigeon is a personal remote-development agent. The idea is simple: the most powerful computer you have access to shouldn't stop being useful the moment you walk away from your desk — and neither should your SI assistant. Send a job from your phone, let the big machine run the tests, crunch the data, or grind through the refactor, and read the results when they land in your inbox.

It belongs to the same family as GitHub self-hosted runners, VS Code Remote tunnels, and Tailscale — legitimate tools for administering your own hardware remotely. And like all of those, its power is the point, not an accident: whoever holds the shared secret has full control of the machine. That's exactly why this project states its threat model plainly instead of burying it. Keep the secret like a password, use a throwaway account, and only ever install the agent on machines you own and operate.

  SI (cloud)                        Your machine
  ───────────