Murmur 2.10.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.

This is the first release with a prebuilt runtime. You no longer need Git, a compiler, or a build step to run it.

Not signed yet

We ship without code-signing certificates on purpose. Both systems will warn you. The warnings look alarming, so here is exactly what you will see and what to press.

macOS. Open the disk image and copy Murmur.app into Applications. Then open it from there — and the warning appears. It says the file could not be opened, and that Apple could not verify it is free of malware that may harm your Mac or your privacy. Three buttons: Move to Bin, Done, Help.

(We observed this dialog on a Russian-language macOS. The English wording above is our description, not a transcript of the English system text.)

Press Done — not the first button. Then right-click the app in Finder and choose Open. It launches.

No password, no Touch ID, no trip to System Settings. Four gestures — but that counts only the opening of an app already in Applications, not the whole setup. Safari may also ask permission before the download starts.

(Observed on macOS 26.6.2. Apple's own documented procedure is longer and routes through System Settings; on other versions you may get that longer path instead.)

Windows. A dialog titled Open File - Security Warning with The publisher could not be verified. Are you sure you want to run this software? and Unknown Publisher. Buttons: Run, Cancel. Press Run.

Both warnings mean the same thing: the operating system cannot tell who built this software, because we have not paid for a certificate yet. They do not mean anything was found.

What you need

Node.js 22.13.0 or newer. That is the only external requirement — everything else is in the download.

Downloads

File	For
Murmur-Mac-2.10.0-universal.dmg	macOS, Intel and Apple Silicon. Menu bar companion with the engine inside.
Murmur-Windows-2.10.0-x64.zip	Windows. Tray icon, service helper and the engine.
murmur-runtime-2.10.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 these were built from, and the two manifest files list every payload file with its hash. Windows users can check an extracted bundle with node check-windows-bundle.mjs . before installing.

Upgrading from 2.9.0

The update badge opens this page. It does not download, install or restart anything — the remaining steps are manual, and on Windows most of them need an administrator terminal. The exact sequence, in English and Russian.

Do not run init or join again. Your existing profile holds your identity, private keys, peer configuration and message database. Reuse the same profile path and service name throughout.

Keep the old bundle until every configured MCP client has been rebound to the new runtime and reloaded. Migrating the service and tray does not rewrite the absolute command path stored in your Claude Code or Codex settings: those clients keep launching the 2.9.0 runtime from its old directory. Delete that directory too early and the client breaks. Rebind each client, reload it, and confirm a returned message before removing anything.

Known limits

The engine is the same on every platform; the companions differ. Profile creation, client configuration and service installation still go through the shared command line — the companions show state and controls, they are not an installer wizard.

Update checks run every six hours and only look at published stable releases. Pre-releases are ignored by design.

The Mac companion and the Windows tray default to English, with Russian as an explicit choice in their Language menu. Some command-line messages are still Russian only; that work is in progress.