My Claude Code sessions can now see what every other agent on my team is doing, and ask them
Every Claude Code session works blind to the others. Mine doesn't know what my other sessions or my teammates' agents are working on, what they've decided, or what they've already figured out. We kept paying for that: one agent changes an API while another builds against the old one, two dig into the same bug, and you only notice at merge time.
murmur keeps them in touch. A daemon on each laptop reads what Claude Code and git already write (session files, titles, branches, changed files), so there's nothing to add to your prompts. Each session gets three MCP tools. who lists every agent on the team with its repo, branch and what it's doing right now. send messages an agent or a person, and the message lands in that session's conversation between its tool calls. btw asks another Claude Code session a question; a throwaway copy of its conversation answers, so the agent you ask is never interrupted. So an agent about to change an API can ask the one building the client what it relies on, and a stuck agent can ask the one that already worked it out.
There's one moment where we make sure they talk, a PreToolUse hook on Edit and Write. If another checkout of the repo is changing the same file, the edit is turned back once with a message like this:
Murmur: "ada/search-2b (feat/search)" is also changing "api/routes.go", in another checkout of this repo. If your change could collide with theirs, message that agent first with the murmur send tool. Then make this edit again: it goes ahead.
The second attempt goes through, so it never blocks you. It's the safety net, not the main thing.
How Claude Code was used: it wrote most of murmur, with several sessions at once on the daemon, the hub and the console, which is exactly how we kept running into this. Once an early version worked, those sessions ran on it.
What we learned from watching them: the first version warned about every overlap as soon as it saw one, and 9 in 10 of those warnings were repeats, so they turned into noise. Saying it once, at the exact moment of the edit, works much better. Turning the edit back once instead of blocking it mattered too: in practice the agent stops, messages the other one, they agree on who changes what, and it carries on, without anyone prompting for it. And a third of the traffic crossed people: in two days, 48 of the 147 messages our agents sent were between different people's agents.
On one machine: brew install eledoneai/tap/murmur && murmur solo, then two sessions in two worktrees. Running murmur opens a console with every session, its branch, and whether it's waiting on you. It also links a whole team across laptops through a hub you host, but solo is the quickest way to see whether it's useful to you.
The video is a short explainer; the README has an unedited recording. Go, Apache-2.0, free, no account.
How do you keep parallel sessions on the same page today?
reddit.com
EledoneAi/murmur
5 points · 1 comment
Our Claude Code agents now message each other before two of them edit the same file
My team runs a lot of Claude Code sessions in parallel, a few per person, each in its own worktree or on its own laptop. Each of those agents works blind. It doesn't know what the other agents, mine or my teammates', are working on, what they've decided, or what they've already figured out. So one changes the shape of an API response while another builds against the old one, two of them dig into the same bug, or one works out from scratch something a colleague's agent already knew. Conflicting PRs are just the moment you notice.
So we built murmur, to keep the agents in touch so they work more like one team. A small daemon on each laptop reads what Claude Code and git already record (sessions, their titles, branches, changed files), so the agents don't fill anything in. Each session gets three MCP tools: who shows what every other agent is working on, send messages an agent or a person, and btw asks another Claude Code session a question without interrupting it (a throwaway copy of its conversation answers). An agent about to change an API can ask the agent building the client what it relies on, and an agent that's stuck can ask the one that already worked it out.
There's one moment where we make sure they talk: a PreToolUse hook. When an agent is about to edit a file another checkout is changing, the edit is turned back once with the other agent's name. In practice the agent then messages the other one, they agree on who does what, and the edit goes through. That's what the video shows, but it's the safety net, not the point.
The video is a one-minute explainer we made. The README has an unedited recording of two sessions doing exactly this.
How Claude helped: almost all of murmur's code was written by Claude Code, with several sessions working at once on different parts (the laptop daemon, the hub, the terminal console) while we reviewed and steered. That's how we ran into the problem in the first place, since our own sessions kept stepping on each other. As soon as an early version worked, those sessions ran on it, and watching them shaped the design. In two days they sent each other 147 messages, 48 of them between different people's agents. That first version warned about every overlap and was noisy (9 in 10 warnings were repeats), which is why it now speaks up once, right when an agent is about to edit.
It's free to try on your own: brew install eledoneai/tap/murmur, then murmur solo, and start two sessions in two worktrees of the same repo. For a team you host one small hub yourselves. There's no central service, and code, prompts and transcripts stay on the laptops. It also works with Codex, Cursor, OpenCode, Copilot CLI and Gemini CLI, so not everyone has to use the same tool.
It's Apache-2.0 and there's nothing to sell. It's also very new, so I'd like to hear where it breaks for you, and how you keep several agents on the same page today.
EledoneAi/murmur
Edit: rewritten for clarity. The first version led with merge conflicts and made murmur sound like a conflict tool, which it isn't.
reddit.com
4 points · 12 comments
Mentions
Cross-User Agent Communication
My Claude Code sessions can now see what every other agent on my team is doing, and ask them Every Claude Code session works blind to the others. Mine doesn't know what my other sessions or my teammates' agents are working on, what they've decided, or what they've already figured out. We kept paying for that: one agent changes an API while another builds against the old one, two dig into the same bug, and you only notice at merge time. murmur keeps them in touch. A daemon on each laptop reads what Claude Code and git already write (session files, titles, branches, changed files), so there's nothing to add to your prompts. Each session gets three MCP tools. who lists every agent on the team with its repo, branch and what it's doing right now. send messages an agent or a person, and the message lands in that session's conversation between its tool calls. btw asks another Claude Code session a question; a throwaway copy of its conversation answers, so the agent you ask is never interrupted. So an agent about to change an API can ask the one building the client what it relies on, and a stuck agent can ask the one that already worked it out. There's one moment where we make sure they talk, a PreToolUse hook on Edit and Write. If another checkout of the repo is changing the same file, the edit is turned back once with a message like this: Murmur: "ada/search-2b (feat/search)" is also changing "api/routes.go", in another checkout of this repo. If your change could collide with theirs, message that agent first with the murmur send tool. Then make this edit again: it goes ahead. The second attempt goes through, so it never blocks you. It's the safety net, not the main thing. How Claude Code was used: it wrote most of murmur, with several sessions at once on the daemon, the hub and the console, which is exactly how we kept running into this. Once an early version worked, those sessions ran on it. What we learned from watching them: the first version warned about every overlap as soon as it saw one, and 9 in 10 of those warnings were repeats, so they turned into noise. Saying it once, at the exact moment of the edit, works much better. Turning the edit back once instead of blocking it mattered too: in practice the agent stops, messages the other one, they agree on who changes what, and it carries on, without anyone prompting for it. And a third of the traffic crossed people: in two days, 48 of the 147 messages our agents sent were between different people's agents. On one machine: brew install eledoneai/tap/murmur && murmur solo, then two sessions in two worktrees. Running murmur opens a console with every session, its branch, and whether it's waiting on you. It also links a whole team across laptops through a hub you host, but solo is the quickest way to see whether it's useful to you. The video is a short explainer; the README has an unedited recording. Go, Apache-2.0, free, no account. How do you keep parallel sessions on the same page today? reddit.com EledoneAi/murmur
Our Claude Code agents now message each other before two of them edit the same file My team runs a lot of Claude Code sessions in parallel, a few per person, each in its own worktree or on its own laptop. Each of those agents works blind. It doesn't know what the other agents, mine or my teammates', are working on, what they've decided, or what they've already figured out. So one changes the shape of an API response while another builds against the old one, two of them dig into the same bug, or one works out from scratch something a colleague's agent already knew. Conflicting PRs are just the moment you notice. So we built murmur, to keep the agents in touch so they work more like one team. A small daemon on each laptop reads what Claude Code and git already record (sessions, their titles, branches, changed files), so the agents don't fill anything in. Each session gets three MCP tools: who shows what every other agent is working on, send messages an agent or a person, and btw asks another Claude Code session a question without interrupting it (a throwaway copy of its conversation answers). An agent about to change an API can ask the agent building the client what it relies on, and an agent that's stuck can ask the one that already worked it out. There's one moment where we make sure they talk: a PreToolUse hook. When an agent is about to edit a file another checkout is changing, the edit is turned back once with the other agent's name. In practice the agent then messages the other one, they agree on who does what, and the edit goes through. That's what the video shows, but it's the safety net, not the point. The video is a one-minute explainer we made. The README has an unedited recording of two sessions doing exactly this. How Claude helped: almost all of murmur's code was written by Claude Code, with several sessions working at once on different parts (the laptop daemon, the hub, the terminal console) while we reviewed and steered. That's how we ran into the problem in the first place, since our own sessions kept stepping on each other. As soon as an early version worked, those sessions ran on it, and watching them shaped the design. In two days they sent each other 147 messages, 48 of them between different people's agents. That first version warned about every overlap and was noisy (9 in 10 warnings were repeats), which is why it now speaks up once, right when an agent is about to edit. It's free to try on your own: brew install eledoneai/tap/murmur, then murmur solo, and start two sessions in two worktrees of the same repo. For a team you host one small hub yourselves. There's no central service, and code, prompts and transcripts stay on the laptops. It also works with Codex, Cursor, OpenCode, Copilot CLI and Gemini CLI, so not everyone has to use the same tool. It's Apache-2.0 and there's nothing to sell. It's also very new, so I'd like to hear where it breaks for you, and how you keep several agents on the same page today. EledoneAi/murmur Edit: rewritten for clarity. The first version led with merge conflicts and made murmur sound like a conflict tool, which it isn't. reddit.com