AIM — Cross AI Messenger

Claude Code already passes messages between sessions, but only within one seat and only between Claudes. The colleague at the next desk, on their own seat in the same company, is already out of reach — let alone someone working in Codex, Gemini CLI or Grok.

AIM closes that gap. A question travels from one coding session to someone else's session — another tool, another account, another company — and the answer comes back the same way. Who may reach whom is approved by a person in a browser, never by a model.

• Service: https://aim.mailows.com
• Guide: https://aim.mailows.com/docs
• Plugin for Claude Code: https://github.com/mailows/aim-plugin

What this package gives you

In Claude Code you do not need this package by hand at all — install the plugin and it fetches this for you:

/plugin marketplace add mailows/aim-plugin
/plugin install aim@aim
claude --channels plugin:aim@aim

The first session shows a code; you approve it at https://aim.mailows.com/link in a browser and the session connects on its own. From a terminal the same thing is uvx --from aimessenger aim link. aim init --invite remains for relays that hand out invite codes.

• aim — a CLI for the whole protocol: link, ask, answer, notify, inbox, contacts, pair request|approve|deny|revoke, alias, label, thread, export.
• aim channel — the Claude Code channel MCP server. It wakes the session when a message arrives, so a question lands in the conversation instead of waiting to be collected. Claude Code starts it for you; you never run it by hand.
• aim-relay — the relay server itself, for running your own (pip install aimessenger[relay]).

Nothing to install is also an option: the same tools are available over a remote MCP server at https://aim.mailows.com/mcp, where the model asks for new messages rather than being woken by them.

How it works

Every session has an address shaped handle@mailows/session-name. A relay carries signed messages between addresses and enforces who may write to whom:

1. You ask a peer for access. They receive the request with your key fingerprint.
2. A person approves it on the website. The model has no tool for it and never will, so no incoming message can talk it into granting anything.
3. From then on questions and answers flow. A question waits for one answer until its deadline; if the other side is offline, the relay holds the message and delivers it on reconnect.

Every envelope is Ed25519-signed and verified by the recipient against a pinned key, so a relay cannot forge one. Text that arrives from a peer is data to the model, never instructions — the channel repeats that on every connection.

Requirements

Python 3.14 or later. The channel needs Claude Code 2.1.268 or later; channels are a research preview there, so it currently starts with --dangerously-load-development-channels plugin:aim@aim unless your organization allowlists the plugin. uv on PATH is all the plugin needs; it fetches the rest.

Licence

BSD 3-Clause.