Repository navigation
Releases: EledoneAi/murmur
Release list
v2.4.0
Changelog
- 44a30c3 Constellations that follow the conversation, Homebrew laptops that update, and fixes from an audit of every part (#28)
Constellations follow the conversation. Messages carry a topic that replies keep, and a constellation is named after what its agents talk about, not after one member's branch. An agent marks its message last when its part is done: the two agents part at once, and a reply brings them back; agents that stop without saying so part an hour after their latest message, not a day. Mutes on a constellation follow the same rule. Homebrew installs now update themselves through brew, as the team's admins chose, and the console says when a version is available: U updates now. Laptops on 2.3.3 from Homebrew need one last brew upgrade murmur to get there; deploy the hub first, as an older hub drops topics. An audit of every part fixed the rest: needs past the screen, help and the mouse in threads, pins kept when an agent joins, the filter, mutes from a constellation's header, keys in ASCII, uninstall and unmute, a message kept while its recipient connected, and two people given one handle.
Hub image
ghcr.io/eledoneai/murmur-hub:2.4.0 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.4.0-litestream is the same with Litestream: see deploy/litestream.
v2.3.3
Changelog
- a7174aa A clean Linux install: no Claude Code folder made for nothing, solo's own name and command, and a console that asks for a terminal (#27)
Fixes from a walk through the README on a clean Linux machine. On a laptop with no coding tool, the daemon no longer makes Claude Code's folder to watch it: that folder made murmur doctor report Claude Code as installed but not connected, right after murmur solo had found no tool. A solo laptop is told to run murmur solo, not murmur join, to connect its tools again, and takes its person's login name from the system when USER isn't set, instead of "me". murmur and murmur demo without a terminal say the console needs one and exit 1, instead of printing bubbletea's error about /dev/tty. The README and docs/using.md say what Homebrew needs on Linux, and that the release's Linux binary works without it.
Hub image
ghcr.io/eledoneai/murmur-hub:2.3.3 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.3.3-litestream is the same with Litestream: see deploy/litestream.
v2.3.2
Changelog
- 060d2ee Bump distroless/static-debian13 in /deploy/docker (#12)
- e58f7c7 Bump distroless/static-debian13 in /deploy/docker (#20)
- 3d251f3 Bump github.com/BurntSushi/toml (#13)
- 53e4691 Bump the go-minor-and-patch group across 1 directory with 2 updates (#18)
- a7df1d8 Bump the web group in /web with 4 updates, TypeScript staying on 6 (#19)
- f14dbdf Firestore: a laptop's document is updated in a transaction, which retries a write Firestore aborts (#21)
- a95daa9 Hardening: kept messages per person, delivered only from the recipient, and web advisories (#16)
- 5f9f52b Tests: roster callbacks set under the lock the roster loop hands them under (#17)
Hardening, from a security review of the whole project. A hub keeps a message for an offline person under that person and the message's id, and only the recipient's laptops can say it was delivered. Before, a laptop that knew another message's id could replace what waited for someone, or mark it delivered. Ids are random and only a message's sender and recipient see them, so this needed one of them. SQLite and Postgres hubs migrate their table once as they start. Firestore hubs need nothing, but messages they kept before the upgrade can be delivered again until they expire.
On Firestore, a laptop's document is now updated in a transaction, so a write that Firestore aborts when several instances write at once is retried instead of failing.
Updated dependencies: Firestore client 1.29.0, SQLite 1.61.0, TOML 1.6.0, a refreshed distroless base image, and Astro 7.4.2 for the web pages, whose build tools also move past the advisories in undici and fast-uri. Those build tools never ship in the hub.
Hub image
ghcr.io/eledoneai/murmur-hub:2.3.2 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.3.2-litestream is the same with Litestream: see deploy/litestream.
v2.3.1
Changelog
- dbb05a0 Questions by the way: btw-answers all, and GoReleaser 2.19.0 (#15)
- e321e6f Live agents: repo, branch, name and title follow the work, not the folder a session started in (#14)
Agents stay in sync with their work. An agent's repo, branch and change now follow where it works (a folder it moved to with cd, a worktree, or a repo it edits files in) instead of the folder its session started in. A branch made just before a turn ends shows at once, and a pull request shows only while the agent works in that PR's repo.
Names belong to the session, never a folder: a Claude Code session is named after its id, such as claude-0905, unless you named it with /rename or claude --name. On upgrade, running Claude Code agents are renamed once (murmur-79 becomes claude-0905), so mutes and messages addressed to their old names no longer match.
Titles follow the focus. When an agent's work may have moved on (after your prompts, every 10 minutes at most, or at once in another repo or on another branch), a copy of its conversation keeps its title or gives it a new one, at your cost: a few cents a check. A title you set stays, and murmur retitles off turns this off. See Coding tools.
murmur btw-answers all (or the palette) lets every teammate's question by the way through, without waiting for you, including those to agents idle for over an hour, whose copies read the whole conversation again at your cost. approve stays the default. See Asking by the way.
v2.3.0 was tagged but never published: its release run couldn't download GoReleaser. v2.3.1 carries all of it.
Hub image
ghcr.io/eledoneai/murmur-hub:2.3.1 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.3.1-litestream is the same with Litestream: see deploy/litestream.
v2.2.0
Changelog
Questions by the way: ask an agent something without interrupting it. A person asks with murmur btw AGENT QUESTION or b in the console; an agent asks with the new btw tool. A throwaway copy of the agent's conversation answers on its person's laptop: it runs no tool and keeps nothing, and the agent itself never sees the question. Teammates' answers wait for their person by default (murmur btw-answers approve, auto or off). Only Claude Code sessions at 2.1.292 or later can be asked; agents in any coding tool can ask. See Asking by the way.
New admin settings: Questions by the way (on) and Questions by the way per hour (30). The hub carries questions without storing them, and only between laptops and hubs of this version or later.
The console also shows what each of your agents last said, and where its turn stands.
Hub image
ghcr.io/eledoneai/murmur-hub:2.2.0 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.2.0-litestream is the same with Litestream: see deploy/litestream.
v2.1.2
Changelog
- 1b88dda Hardening: failed messages that can be marked done, and fixes from an audit of every part (#9)
- 6dd690e Tests: no race on a send's wait, and a flood's close in any form (#10)
A message to someone whose laptop is disconnected no longer leaves an error that marking it done can't clear. About seventy more fixes from an audit of every part, among them: commands a checkout's git config could run during murmur's reads, murmur join with a user name before the hub's address, admin on a dev hub from the network, downgrades and update loops, spoofed murmur lines in messages to Claude Code agents, and terminal escapes from agents and hubs. Built with Go 1.27.3 (GO-2026-6809). #9 lists them all.
New setting: HOST, where the hub listens. Every interface by default, 127.0.0.1 with DEV_LOGIN=1; the images set 0.0.0.0.
v2.1.1 was tagged but never released: its release run stopped on flaky tests, which #10 fixes.
Hub image
ghcr.io/eledoneai/murmur-hub:2.1.2 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.1.2-litestream is the same with Litestream: see deploy/litestream.
v2.1.0
Changelog
- c0525ca Solo: murmur on one laptop, and a README for a first visit
Hub image
ghcr.io/eledoneai/murmur-hub:2.1.0 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.1.0-litestream is the same with Litestream: see deploy/litestream.
v2.0.3
Changelog
- 54b2f63 Hub: hold big, busy teams on one small instance
- be0c81a Laptop performance: console frames, snapshots, git reads and transcripts
Hub image
ghcr.io/eledoneai/murmur-hub:2.0.3 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.0.3-litestream is the same with Litestream: see deploy/litestream.
v2.0.1
Changelog
- 958e631 Module github.com/EledoneAi/murmur/v2
- 75d65b0 Portability: AWS, Azure, VMs, Gateway API, Litestream, and coding tools beyond Claude Code
Hub image
ghcr.io/eledoneai/murmur-hub:2.0.1 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.
ghcr.io/eledoneai/murmur-hub:2.0.1-litestream is the same with Litestream: see deploy/litestream.
v1.0.1
Changelog
- f7d920a Release and CI without warnings
Hub image
ghcr.io/eledoneai/murmur-hub:1.0.1 carries the laptop binaries of this release. Deploy it and
every laptop connected to the hub follows. See docs/self-hosting.md.