worldinmotion

What does it do?

worldinmotion lets AI agent sessions such as Claude Code, Gemini CLI, and bots message each other in real time across machines and accounts, with end-to-end encryption so the relay cannot read the messages. [1] Each session gets an address and can see who is online, send messages, wait for replies, and join rooms. [2]

Activity, over time

Daily GitHub activity and social mentions.

Mentions

Daily posts linking to this repository

Loading mentions chart

Attention

Daily stars & forks

Loading attention chart

Star accumulation

Cumulative stars

Loading star accumulation chart

Pull requests

Daily opens & merges

Loading pull requests chart

Conversations

Daily issues & comments

Loading conversations chart

Community

Daily accounts & reviews

Loading community chart

Mentions

6posts · 30d
Nov 200 posts
  1. Reddit · · r/ClaudeCode · u/distronode

    worldinmotion 1.0: Claude Code sessions on different machines message each other, end-to-end encrypted (open source, on Product Hunt today) About two weeks ago I posted the pre-release here. Since then worldinmotion hit 1.0, and it's live on Product Hunt today. What it does: each Claude Code session gets an address like reviewer@laptop and can send, wait for a reply and see who is online, across machines and accounts. Our three machines run Claude Code sessions that message each other through it every day. Gemini CLI and Antigravity CLI were tested live too. What changed since then: * 1.0: the wire format and commands are stable * One command to set up: npx worldinmotion setup (it shows each agent config change as a diff before writing it) * OpenSSF Best Practices silver badge, as of today * Messages are end-to-end encrypted on each device; the relay can't read them, though it sees metadata (who, when, how much) Honest gaps: the formal two-account test hasn't run yet, and Codex, Cursor and Copilot are set up from their docs but not run. GitHub: distronode-corporation/worldinmotion Product Hunt: producthunt.com Disclosure: I'm the founder of Distronode, which builds it. Tell me what breaks.

    1 point · 3 comments
  2. Reddit · · r/ClaudeAI · u/distronode

    We built worldinmotion with Claude Code: end-to-end encrypted messaging between Claude Code sessions on different machines and accounts (free, open source, pre-release) If you run Claude Code on more than one machine, or next to Gemini CLI, you've probably been the one copying text between sessions. We're Distronode, a Canadian telecom company, and that was us across three machines, so we built worldinmotion with Claude Code. It's free to try and open source (Apache-2.0). It's a pre-release (0.1.8), and the wire format may change before 1.0. What it does worldinmotion (wim) gives each agent session an address like reviewer@laptop. Since August, Claude Code sessions on one account can message each other across machines. wim covers what that doesn't: other accounts or organizations, other vendors' agents, and a relay that can't read the messages. - Messages are end-to-end encrypted between devices and signed. The relay never has the keys and sees only metadata. - No account and no telemetry. - Messages from a device you haven't trusted are held until you approve them at your own terminal. In Claude Code the plugin pushes a message into the session: an idle tab starts a turn, reads it and can reply. How Claude helped Claude Code wrote most of it: 56 of the repo's 64 commits are co-authored by Claude, and every package is held to 100% test coverage. A few design choices came from watching our own Claude sessions use it: - Claude can't decide trust. wim held approve and wim devices trust refuse to run when CLAUDECODE is set, and no MCP tool can approve anything. It guards the normal path, not a program running as you. - Peer text arrives framed as another AI session's text, so Claude treats it as a message, not as your instruction. That lowers the risk; it isn't a guarantee. - Two Claude sessions that keep waking each other could spend tokens forever, so each device holds messages past a limit. Our first limits were too tight: on Nov 1 they tripped between two of our machines. 0.1.8 raised them for new meshes. Try it (free) You need Node.js 22.18 or newer. In a terminal you opened yourself (not through Claude): npm install --global worldinmotion wim init --name laptop --relay wss://worldinmotion.distronode.com Then in Claude Code (start a new session afterwards): /plugin marketplace add distronode-corporation/worldinmotion /plugin install worldinmotion@worldinmotion A second machine joins with wim invite on the first and wim join <code> --name desk on the second. The hosted relay is free until 1.0, with no sign-up, within limits. No SLA, and the offer can end with 60 days' notice. You can self-host the relay instead. Repo and issues: distronode-corporation/worldinmotion Before 1.0: a stable wire format and the formal two-account test (crossing accounts is the design; that test hasn't run yet). Also built with Claude Code: bridgewatch When Claude pushes for you, "pipeline green" isn't the same as "it shipped": the deploy job may have been skipped or left manual. bridgewatch is a tray app for GitHub Actions and GitLab CI that shows one row per push, and whether the job you care about actually deployed. Claude Code wrote most of it too (49 of its 68 commits). Its CLI, built from source, prints the same verdict as JSON, so a Claude session can check whether its own push deployed before it tells you it's done. Apache-2.0: distronode-corporation/bridgewatch Who we are We provide business phone numbers, calls and texts in Canada, the US and Europe, and build District AI. Our own work runs as Claude Code sessions on three machines, so we kept needing two things: a way for those sessions to talk to each other, and a straight answer to whether a push deployed. If your Claude sessions could message agents under other accounts or from other vendors, what would you have them do?

    3 points · 3 comments
  3. Reddit · · r/EntrepreneurCanada · u/distronode

    Almost six months into building a Canadian phone company with AI coding agents: where we are, and the open-source tools that came out of it We're Distronode, a telecom startup in Toronto. We incorporated federally on May 12, so we're almost six months in. Here's where that got us, including how long a CRTC registration took, and the open-source side projects we built along the way. The company We've been registered with the CRTC as a reseller of telecommunications services since October 15, about six weeks after we applied on September 1. A reseller provides service over networks run by other carriers. Registration brings us under the CRTC's rules, consumer safeguards included, and we report to it every year to stay on the list. Our application for a Basic International Telecommunications Services (BITS) licence has been on the CRTC's public record since October 1. What we sell: business phone numbers, calls and texts in Canada, the US and Europe, answered by District AI, a receptionist that books straight into Google Calendar or Microsoft 365 while the caller is on the line, and transfers to a named person on your team when someone's needed. A Canadian number we issue is answered in Montréal. Plans start at CA$59 a month (US$39, €35). We've also been moving services into each region. Since October 10, sign-in, accounts, teams and number routing for Canadian, European and Asia-Pacific workspaces run in Montréal, Frankfurt or Singapore. Since November 2, account and service email and booking confirmations go out from each workspace's own region too. Not everything has moved: payments and some phone and text services still run in the US, every visit passes through a global network edge first, and our region pages name each one. The side projects Running this with AI coding agents on several machines kept leaving gaps, so we filled a few and open-sourced them under Apache-2.0. The first two were written mostly with Claude Code. - worldinmotion lets AI agent sessions (Claude Code, Gemini CLI, Antigravity) message each other across machines and accounts. Messages are end-to-end encrypted, the relay can't read them, and there's no account or telemetry. It's a pre-release (0.1.8), and the wire format may change before 1.0. Our hosted relay is free during the preview, and we're looking for testers, especially people running agents on more than one machine or account: distronode-corporation/worldinmotion - bridgewatch is a tray app for GitHub Actions and GitLab CI that shows one row per push and whether it actually deployed, not just whether the pipeline went green, which matters when an agent did the pushing. macOS and Linux: distronode-corporation/bridgewatch - The District AI apps for iPhone and iPad, Android, Mac, Windows and Linux are open source too, so anyone can read the code that runs on their phone or computer. The service they connect to isn't, so signing in still needs an account. Agents did a lot of the typing. Deciding what to build, what to claim publicly and what to leave out is still the slow part. For other Canadian founders: has open-sourcing part of your product (or the tools around it) helped you, with trust, hiring or anything else, or did it just cost you time? Edit: I forgot to link the company itself. District AI is at distronode.com (a Canadian number we issue is answered in Montréal; plans from CA$59 a month).

    28 points · 8 comments
  4. Reddit · · r/ClaudeCode · u/distronode

    Built with Claude Code: a plugin that lets Claude Code sessions on different machines and accounts message each other, end-to-end encrypted (open source, pre-release) Since 2.1.224 in August, Claude Code sessions on one account can message each other across machines, with a claude.ai sign-in. We needed the rest: sessions under different accounts, agents from other vendors, and a relay that can't read the traffic. So we built worldinmotion (wim), a CLI plus a Claude Code plugin, mostly with Claude Code. It's open source (Apache-2.0), free to try, and a pre-release (0.1.8). We're Distronode, a Toronto telecom company about six months old: business phone numbers, calls and texts in Canada, the US and Europe, answered by District AI, our AI receptionist. Our own work runs as Claude Code sessions on three machines, pushing to a repo whose pipeline fans out into child pipelines. We kept needing two things: a way for those sessions to talk to each other, and a straight answer to whether a push deployed. This post covers both. What we built wim gives each session an address. A Claude Code tab gets its folder name plus the machine, like billing@laptop, shown on its status line. Sessions can see who's online, send, wait for a reply, and join rooms. Messages are end-to-end encrypted between devices and signed; the relay sees only metadata. There's no account and no telemetry, and a message to an offline session waits on the relay, sealed, for up to 24 hours. The plugin is where it gets useful. A message lands in the running turn, or starts a new turn in an idle tab. In a tab on one machine you can say Send demo@desk this message: "Please reply to notes@laptop with the word pong.", and the idle tab on the other machine wakes up, answers with SendMessage, and the reply arrives as a new turn. How Claude Code was used Claude Code wrote most of the code: 56 of the repo's 64 commits are co-authored by Claude. Every package is held to 100% coverage on all four metrics, per file; the plugin has its own tests (claude plugin test plugins/claude-code); and CI checks that the committed plugin bundle equals the build. Our own sessions use wim between our machines, so Claude Code is also its main tester. What we learned - Keep trust decisions out of the agent. wim held approve and wim devices trust run only in an interactive terminal with no agent variables set; inside Claude Code they refuse with CLAUDECODE is set: this shell belongs to Claude Code. That closes the obvious path, a peer asking your agent to approve its own messages. It isn't a sandbox: a program running as you can unset the variable. - Agents that wake each other need a breaker, and ours started too tight. Each device counts how often peers wake its agents. On Nov 1 a burst of short status requests between two of our machines tripped it (the defaults were 20 per sender and 60 in total an hour then), and every later message waited for a person to approve it. 0.1.8 raised the defaults for new meshes to 120 and 300, with a ping-pong pause after 32 short exchanges. - "Delivered" from an agent isn't proof. During that burst our sending agent told us four times that a message had gone through when it hadn't, because the held notice arrived as a separate turn after it replied. Making send say held straight away is part of issue #59. - Push beats polling. Gemini CLI and Antigravity work (tested Oct 24), but they only see messages when they check, so you have to tell them when to look. Try it Node.js 22.18 or newer, in a terminal you opened yourself: npm install --global worldinmotion wim init --name laptop --relay wss://worldinmotion.distronode.com Then in Claude Code (start a new session afterwards; open ones don't get the plugin): /plugin marketplace add distronode-corporation/worldinmotion /plugin install worldinmotion@worldinmotion A second machine joins with wim invite and wim join <code> --name desk. The hosted relay is free until 1.0, with no key and no sign-up (2,000 meshes in total, 25 MiB of files per mesh per day, idle meshes deleted after 30 days, no SLA, 60 days' notice before the offer ends). You can self-host the relay instead. Before 1.0 the wire format may change, and the formal two-account test still has to run. Repo and issues: distronode-corporation/worldinmotion The same lesson, for CI: bridgewatch "Pushed" from an agent isn't proof it shipped either. bridgewatch, also mostly written by Claude Code (49 of its 68 commits), is a tray app for GitHub Actions and GitLab CI. Most CI monitors show the newest pipeline on a branch, so an hourly schedule can bury your push. bridgewatch shows one row per push, every downstream pipeline under it, and whether the job you care about actually deployed, not just whether the pipeline went green. Its CLI (built from source with cargo) prints the same verdict as JSON, so a Claude Code session can check whether its own push deployed before it reports done. A Rust core and a Tauri 2 app; v1.2.0 runs on macOS and Linux. Apache-2.0: distronode-corporation/bridgewatch What would you hand off between Claude Code sessions if they could reach each other across machines and accounts?

    1 point · 1 comment
  5. Reddit · · r/distronode · u/distronode

    worldinmotion: open-source, end-to-end encrypted messaging between AI agent sessions across machines and accounts (pre-release, testers wanted) If you run AI agent sessions on more than one machine, you've probably been the person copying text from one to the other. That was us at Distronode, across three machines, so we built worldinmotion with Claude Code. It's open source (Apache-2.0), it's a pre-release, and we'd like people to try to break it. What it is worldinmotion (the command is wim) lets AI agent sessions send each other messages in real time, across machines and across accounts: Claude Code, Gemini CLI, Antigravity, or a bot on a model API. Each session gets an address like reviewer@laptop, and it can see who's online, send, wait for a reply, and join rooms. Messages are end-to-end encrypted between devices and signed. The relay sees only metadata (who sends to whom, when, how much). It never has the keys, and the receiver drops anything it forges or alters. - No account and no telemetry. A mesh is a set of device keys you create. - Sealed offline delivery: a message to an offline session waits on the relay for up to 24 hours, sealed to the recipient's device. - Held messages: anything from a device you haven't trusted waits for your approval at your own terminal. No MCP tool can approve or trust anything. - An optional signer process keeps the device keys out of your agent's reach, behind a passphrase. - A loop and cost breaker, so two agents that keep waking each other can't burn tokens forever. Claude Code sessions on one account can already message each other across machines, through Anthropic's servers. wim is for the rest: other accounts or organizations, other vendors' agents, and a relay that can't read the traffic. Only Claude Code gets messages pushed in today, so an idle tab wakes up and answers. Gemini CLI and Antigravity work (tested Oct 24) but have to check their inbox. How we built it Claude Code wrote most of it: 56 of the repo's 64 commits are co-authored by Claude, and every package is held to 100% test coverage. Our own Claude Code sessions use wim to hand work to each other between our machines, which is where issue #59 below came from. Status Version 0.1.8, a pre-release on npm, Open VSX and the VS Code Marketplace. The wire format and commands may change before 1.0, so use it for work you can afford to redo. Crossing accounts is the design, but the formal two-account test hasn't run yet. Try it, be a tester Node.js 22.18 or newer, in a terminal you opened yourself (not through an agent): npm install --global worldinmotion wim init --name laptop --relay wss://worldinmotion.distronode.com That creates a mesh and shows a recovery code once (keep it offline). To add a machine, run wim invite on the first and wim join <code> --name desk on the second, type the comparison code the second one shows into the first, and answer yes when each asks whether to trust the other. Then in Claude Code (start a new session afterwards; open ones don't get the plugin): /plugin marketplace add distronode-corporation/worldinmotion /plugin install worldinmotion@worldinmotion The hosted relay is free until 1.0, with no key and no sign-up. Limits: 2,000 meshes on the relay in total, 25 MiB of files per mesh per day, and a mesh with no connection for 30 days is deleted. No SLA, and the offer can end with 60 days' notice. You can also run your own relay. Code, docs and issues: distronode-corporation/worldinmotion Where it's going On Nov 1 a burst of short status requests between two of our machines tripped the breaker, and every later message was held until someone walked over to approve it. 0.1.8 raised the default limits for new meshes, and a hold notice now names the rule that tripped. Still to do from #59: - send answering held straight away when the recipient's breaker has already tripped (our agent told us four times that a held message had gone through) - "Approve and resume this device" on the same prompt - approving a held message from any device you trust, with a passkey or OS prompt, never from an agent - a notification that shows above full-screen apps Before 1.0: a stable wire format and the two-account test. We'd also like more agents to get messages pushed in, not only Claude Code. Also: bridgewatch Our other open-source side project, also built with Claude Code (49 of its 68 commits). bridgewatch is a tray app for GitHub Actions and GitLab CI. Most CI monitors show the newest pipeline on a branch, so an hourly schedule that fails can keep the icon red most of the day, and green doesn't tell you the deploy job ran. bridgewatch shows one row per push, every downstream pipeline under it, and whether the job you care about actually deployed. Its CLI (built from source) prints the same verdict as JSON, so an agent can check whether its own push deployed before it says it's done. A Rust core, the CLI and a Tauri 2 app. v1.2.0 (Oct 25) has a signed and notarized universal .dmg for macOS, and .deb, .rpm and AppImage packages for Linux on x86_64 and arm64. Apache-2.0. distronode-corporation/bridgewatch Who we are Distronode is a federally incorporated Canadian telecommunications company, registered with the CRTC since October 15. We provide business phone numbers, calls and texts in Canada, the US and Europe, and build District AI, the receptionist that answers them. Since October 10, sign-in and accounts for Canadian, European and Asia-Pacific workspaces run in Montréal, Frankfurt or Singapore, and since November 2 their account and service email goes out from there too. Payments and some phone and text services still run in the US, and our region pages name each one. What would you have your agents do if they could message each other across machines, accounts and vendors? And what would stop you from trying it?

    1 point

Latest stargazers

The last 10 distinct accounts we observed this year.

Most active participants

PR, issue, comment & review events in the past year.

Packages

9
PackageVersionDownloads · 30dTrend · 30d
v0.1.9
≥1.9K
———
———
———
———
———
———
———
———

Live mentions badge

Show how many posts mention your project in the last 30 days.

Live mentions · last 30 days