Murmur

Context, made visible

What the model is sent, turn by turn

Murmur doesn’t assemble prompts. It picks which session a message goes to, and that decides what the model sees.

Every turn sends the agent’s setup: its prompt and tools.
Never sent: other branches, other conversations, and notes you haven’t handed over.

A branch carries its own path

Its path from the start, and nothing from its siblings. That’s where a side quest saves.

Ask a side question in one long chat, and every later turn carries it.
A new branch’s first turn reloads its history. Caching should soften that; it hasn’t been measured yet.

Sever stops sending what’s above

The conversation stays as it was. Only what the next turn carries changes.

A long line: every turn sends all of it.
Below the cut, a fresh session starts from a short transcript: what was said, not the files that were read.

A summary stands in for the turns it covers

From the map’s Select tool: Summarise and compact, or Continue with these for exactly the messages you pick.

Select the turns a summary should stand in for.
Writing it is a turn of its own: it pays off when the conversation carries on long enough below it.

The ring in the message box shows how much of the context window the branch on screen uses, as the agent reports it. Read the full explainer or take the full tour.

Think in branches

Follow every side quest. Murmur works with the Claude or ChatGPT plan you already pay for.

Download for Mac

For Macs with Apple silicon on macOS 13 or later. Needs Node.js, and Claude Code 2.1.293 or later or Codex, signed in. Set up your Mac