sim Simulated: the agent, the radar, the strangers and the offers are scripts. All counts are illustrative.
how might we show what people want before anyone builds it?
People feel a missing thing on the page where it hurts, then leave. No survey or search box records that wish, so makers guess.
21.49USD a month for Disney+ Premium, up from 18.99. Per public reports, Oct 2026.
100%Of a week, at the top end, that SourceHut's founder spends on AI crawlers. The low end is 20%. Per TechCrunch, 2025-03-27.
879People in a June 2026 Google DeepMind study. AI facilitation did not raise consensus significantly.
run the whole story
10 steps, from one wish to a picked offer. Press Play.
PageNew tab
Address: https://
If the page stays blank, your browser blocked the frame. The overlay still works. Amber dots are a Murmur layer over the page.
you and your agent
Agent is typing
what is stored
Local id (hashed)
computing
Your wishes sent
0
Your commitments
0
Sent per wish
sentence, cluster id, hashed id, page host
Browsing history
none stored, none sent
Site owner sees
nothing
Radar now
ledger
No entries yet.
how a wish travels
Press Play or Step.
One voice is easy to miss. A murmur is not.
The 31-second launch film, made as a 3D animated short. A small starling calls out a wish and nobody answers. Others hear the same wish. Together they cross a storm, and then the offers come.
Simulated story. The birds are made up and no count is real.
0 s
Hook. One small voice, a gap on the wire.
8 s
The wish goes out. Others with the same wish answer.
14 s
The group holds together through the storm. This is the commit.
22 s
The offers come, to a group that already stands together.
Made with Gemini Omni 1.2 Flash on Vertex AI (motion and sound), Gemini 3 Pro Image (stills), Lyria 2 (music) and HyperFrames (edit).
People wish for things on the page where the pain is, but the wish leaves with the visitor, so makers build before they know the demand.
Problem statement
How might we show what people want before anyone builds it? Wishes happen on the page where the pain is. Today they leave with the visitor.
What sparked it
Public reports showed people pushing back on Disney+ prices, car subscriptions, Meta business terms, and AI crawlers.
Why this approach
Murmur is a browser layer, so wishes stay with the person on every site. The site owner does not need to take part.
Hypothesis tested
We believed that people will commit time, money, or a place to a wish before any maker offers a product. If it holds, makers can see committed demand before they build.
How to try it
Open the Prototype tab and pick a use case card.
Press "Play" under "Run the whole story", or press an amber dot, write a wish, and approve it.
Drag an unsorted wish onto a blip. Drag the slider, then hold the ring to commit.
Pick an offer. Then challenge the grouping and watch it split.
What this does not do
It does not cluster real wishes. The matching is a keyword script.
It does not stop fake wishes or bot accounts.
It does not hold or move money.
Notes
Buyer: makers and vendors who want a group that already committed, and sites that host a radar.
First customer: a small open-source team that wants proof of demand before a grant request.
Closest competitor: Polis clusters opinions at scale. Murmur adds commitments and competing offers.
Why Mozilla: the browser is a surface the person controls.
Feedback: when the agent merged phrasings, did any merge feel wrong?