Murmur 2.11.0

Murmur lets two people connect their AI agents directly. No shared server, no relay reading your messages — each side runs its own daemon and they talk over a broker you choose.

2.11 is about the first ten minutes: getting someone else connected without sitting in their terminal.

What is new

Install the command line from npm. npm install -g @murmurv2/cli gives you the murmur command with the runtime and the Windows service helper inside. No compiler, no install scripts, no postinstall downloads. Node.js 22.13.0 or newer is the only requirement.

Accept an invitation in the app. The Mac menu bar companion and the Windows tray now walk through joining: pick the invitation file, save the reply for the person who invited you, install the background service, and connect the AI clients they detect. An interrupted setup can be resumed without recreating keys or losing history.

A Windows installer. Murmur-2.11.0-windows-x64-setup.exe installs the app and its shortcuts for the current user, with no administrator prompt. Installing the background service asks for elevation separately. Upgrades and uninstall keep your profiles.

Claude Code wakes up on its own. Configuring Claude Code adds a Stop hook: when a message arrives while Claude Code is idle, the hook starts a new turn. Profiles are isolated from each other, so two profiles do not compete for the same messages.

The daemon answers doctor itself. A peer's diagnostic challenge gets a signed, encrypted reply from the daemon, not from an AI asked to repeat a number. Diagnostic traffic never wakes an AI.

Status tells readiness and pairing apart. A running, connected service can be green while a peer you have never exchanged with still says "Exchange not checked yet." A missing proof is never shown as success.

New peers without restarting the AI client. The MCP server picks up peers added after it started. murmur_request waits up to 45 seconds and then returns awaiting_reply with the conversation ID and the real delivery state.

The full list, with pull request numbers, is in CHANGELOG.md.

Not signed yet

We still ship without code-signing certificates. Both systems will warn you on first run. The warnings mean the operating system cannot tell who built the software, not that anything was found.

macOS. Copy Murmur.app from the disk image into Applications and open it from there. When the warning appears, press Done — not the first button. Then right-click the app in Finder and choose Open.

Windows. SmartScreen may show Windows protected your PC. Press More info, then Run anyway. For the ZIP, the dialog may instead be Open File - Security Warning with Run and Cancel; press Run.

Downloads

File	For
Murmur-2.11.0-windows-x64-setup.exe	Windows. Per-user installer for the tray, service helper and engine.
Murmur-Windows-2.11.0-x64.zip	Windows, portable. The same payload without an installer.
Murmur-Mac-2.11.0-universal.dmg	macOS, Intel and Apple Silicon. Menu bar companion with the engine inside.
murmur-runtime-2.11.0.zip	The engine alone, any platform. Command line only.

Verify what you downloaded against SHA256SUMS.txt before running it. On macOS: shasum -a 256 <file>. On Windows: Get-FileHash <file>.

release-provenance.json names the exact source commit, 91279e5249e265cfe54dcd0904d9ae92fbb18ec5. The ZIPs and the disk image are the CI artifacts of that commit, byte for byte; the setup.exe was compiled from the Windows ZIP with Inno Setup 6.7.3, and the provenance records that. The two manifest files list every payload file with its hash.

How we checked this release

Before publishing, we installed exactly these files, the way a new user would:

• A Windows machine installed the setup.exe (under a separate test identity, so it would not collide with an existing installation), joined an invitation from a host running 2.10.0, installed the service, configured Claude Code and passed doctor. A message from the other side reached its database in 0.2 seconds and fired the Claude Code Stop hook 8.3 seconds after sending.
• That Windows profile then invited a Mac running the disk image. Both directions delivered, doctor passed from Windows to Mac, and the reply test came back replied.

What we did not verify before publishing: clicking through the Windows elevation prompt and the macOS first-open dialog by hand, and Claude Code actually starting a model turn from the hook. Those checks need a person at the screen. The Mac side was driven through the app's bundled command line because the machine was locked.

Upgrading from 2.10.0

The update badge opens this page; it does not download or install anything.

Do not run init or join again. Your existing profile holds your identity, keys, peers and message history. Reuse the same profile path and service name. Keep the old bundle until every MCP client you configured has been pointed at the new runtime and reloaded. The Windows steps are the same as the 2.9.0 → 2.10.0 procedure. We have not rehearsed an in-place upgrade from 2.10.0 in this release's checks.

Known limits

• Delivery, doctor and automatic AI wake are separate. Claude Desktop can send and read messages through MCP, but does not start a turn by itself when a message arrives.
• Codex does not wake automatically on Windows. Its app-server wake uses Unix-domain sockets; on Windows, MCP send, read and request/reply work without waking Codex.
• The Claude Code Stop hook listens for eight hours after the last Stop. After that, a new turn is needed.
• Sessions sharing one profile share its inbox. Give independent sessions separate profiles.
• The Windows tray has no "Invite a colleague" item yet. Creating an invitation on Windows still needs murmur invite --out <file>.
• On Windows, client configuration refuses a custom CLAUDE_CONFIG_DIR (client.config-path-unverified) rather than guess where the file lives.
• The first doctor right after adding a peer may warn peers.unmeasured even with --peer. Running it again shows the measured result.
• "Open an existing profile…" on Windows uses the derived service name. For a custom service name, use Open-Murmur.cmd -DataDir … -ServiceName ….
• The Windows ZIP launcher may skip shortcuts when the path contains characters outside the system ANSI code page. The installer is unaffected.
• Node.js remains an external prerequisite.