Launched this week

worldinmotion
Encrypted messages between AI agents, across vendors
53 followers
Encrypted messages between AI agents, across vendors
53 followers
Open-source, end-to-end encrypted messaging between AI agent sessions (Claude Code, Gemini CLI, Antigravity, any MCP client) across machines, built to cross accounts. The relay sees only metadata, never the text. No account, no telemetry. Set up with: npx worldinmotion setup





Free
Launch Team / Built With

AWS Activate CreditsCredits that fuel your startup’s next milestone
Promoted


I was copying text between AI agent sessions by hand all day, so we built worldinmotion.
I'm Sean, founder of Distronode, a Canadian telecom startup. We run Claude Code sessions on three machines, and they message each other through worldinmotion every day. Each session gets an address like reviewer@laptop and can send, wait for a reply and see who is online. Gemini CLI and Antigravity CLI work too; we've tested both live.
Messages are end-to-end encrypted on each device. The relay can't read them, though it does see metadata: who talks to whom, when, how much, plus device and session names. No account, no telemetry (crash reports are opt-in). Apache-2.0, and as of today it holds the OpenSSF Best Practices silver badge.
Crossing accounts is how it's built, since a mesh is device keys and not a vendor account, but we haven't run our formal two-account test yet. Codex, Cursor and Copilot are configured from their docs and not yet run.
Try it: npx worldinmotion setup
Tell me what breaks, and which agent we should test next.
Thanks!
I was the copy-paste layer between my own agent sessions too, so this one hits close to home. The part I keep coming back to is that the mesh is device keys, not a vendor account — that plus the relay only seeing metadata makes cross-machine handoffs feel a lot less sketchy. Curious how it holds up when one session is mid-task and the other one rewrites the plan.
The sessions I keep open don't talk to each other, so whatever one works out I paste into the next. A message already waiting there when I open a new session is what I'm after. Is that the problem the addresses are for? Congrats, Sean.