Murmur: how client feedback on the page came to life

On Wednesday an agency owner wrote to me with a problem that had nothing to do with AI. He had rebuilt a client's site on staging, the client was a charity, and the trustees had to look at every page and say what was wrong before anyone would sign off. The tools built for that ask the reviewer to install something or make an account. Trustees do neither. What he wanted was a link. Two days later it shipped as Murmur, in plugin 8.9.0.

The ask, in his words

Send the trustees one link. They open it on whatever they have, tap the thing they do not like, write a sentence, done. The notes come back to him, and ideally the agent that built the site gets to read them and do the work. No login, because nobody is going to remember a password for a site that does not exist yet. No install, because the reviewers are not technical and should not have to be.

Respira already had half of this. A share link could open a staged draft for anyone, for a short window, so a client could look. It just could not listen. The page went out, the comments came back by email as screenshots with arrows drawn on them, and someone had to translate "the second box on the left" into an element a builder knows. That translation is the job nobody wants, and it is exactly the job an agent is good at, if the note arrives in a shape it can use.

What a note has to carry

So the design question became: what does a reviewer's tap have to record for an agent to act on it without guessing. The answer is four things, and every murmur carries all four.

• The page, as a post id and its address, so the note lands on the right thing even after the page is duplicated.
• The words under the finger, quoted, when the spot is text.
• The element, as the builder itself names it, so a Divi module or a Bricks element is addressed by its own id, plus a CSS path as the fallback.
• A label in plain words: the picture, the button, this section. A reviewer who taps a background image should see that they tapped a background image, and so should the agent.

With that shape, "apply the murmurs" is one instruction. The agent makes a duplicate of the page, walks the notes, finds each element by its id, makes the change, reads the page back, and resolves each note with the snapshot id of the write. The reviewer sees the reply on the page. The owner sees the receipt in the dashboard. Nothing touched the live page.

The part that had to be right before anything else

A link that opens a draft to anyone without a login is a door, so the door got the most attention. Each link is signed by the site itself, with its own salt, over the session id and the expiry. It lifts only the pages it names, and only for the person holding it; every other visitor still sees the site as it is. It expires after one to ninety days and can be revoked at any moment from the dashboard or by an agent. The review bar is a single script served by the site; it loads nothing from anywhere else, and every word a reviewer types is treated as text, never as markup. Site scope, where the reviewer may browse every published page with the bar on, is only offered on sites marked as staging unless the owner confirms it.

i went through the same checklist a security researcher would, and then a security audit went through it again this week. Reviewer text is fenced from the agent the same way every other visitor input is: quoted, never followed as an instruction.

Why it is called Murmur

i asked for a Respira name that did not sound like software. Respira means breathe. A murmur is the thing a client says under their breath while looking at a page: "this photo is from before the renovation", "the chair goes first". Quiet, specific, and the whole point. The feature is the link; the murmurs are what comes back through it.

What changed between the first cut and the release

The first version anchored a note to text, and the first person to try it (me, on my own site) tapped a picture and could not tell what had been recorded. That is where the label in words came from. Reviewers can now leave an email if they want a reply. A link can be made without an agent at all: paste the page addresses on the Murmur page of the dashboard, choose how long it stays open, copy it. The same page lists every link, copies it again on demand, and revokes it. And the notes reach Respira AER, where "apply the murmurs" is a shortcut, and any AI connected through Respira, where the seven review tools are plain tools.

Where it sits

Murmur is part of the Builder plan and up, the same line as Site memory. It shipped on 12 September in plugin 8.9.0 and MCP server 8.3.24. The product page is at respira.press/murmur, and the dashboard page is Murmur: feedback links. If you are the agency owner who asked: the trustees can start on Monday.