Playbooks · Everyday tasks
Simon Willison's mystery beep, triangulated
Written November 10, 2026
Something in a room full of unpacked boxes beeped every so often, too rarely to find by standing and listening. Five spare devices, a Python server, and Claude Code narrowed it to about 40 cm — an old carbon monoxide detector asking for new batteries.
The problem
An intermittent beep in a box room, with the beeps far enough apart that standing in the room and listening did not work, and too many boxes to dig through one by one. The fix did not need a new device. It needed the microphones already in the house — two iPads, a phone, a MacBook Pro, and a Surface Ultra — turned into a sensor network.
How it worked
Simon Willison's account, published November 9, describes a system called Beep Locator, built with Claude Code. A Python web app runs the server and shows the main interface. The other devices join by QR code or URL and act as listeners, connecting over WebSockets and opening their microphones in the browser. Each listener keeps a 60-second buffer of recent audio and runs a beep detector — a Fast Fourier Transform with a high-pass filter — that reports candidate beeps to the server.
When a beep is reported, the server has a device play a short chirp, then asks every listener to upload a clip from about 0.6 seconds before the beep to 0.8 seconds after the chirp. The chirp lets the clips be lined up with each other, which is the step that makes locating the beep possible. Recorded sounds can be replayed from each device in turn, and a button marks a recording as the mystery beep, so later sounds are compared against it and the position gets tighter over time.
Two details made it usable in practice. A clap mode let Willison test the system by clapping in different places and watching the claps land on the map. And a "rough mode" let him drag the device icons to roughly where they were, after the automatic self-location — devices playing sounds at each other to work out their positions — did not work particularly well.
The result
Willison's verdict, in his words: "The system worked as intended. It gave me the position of the beep to within about 40cm, then I dug through that specific pile of boxes and found an ancient carbon monoxide detector that desperately wanted its batteries replaced." The beep was at 3345 Hz, and the map in his post shows the located position within about 41 cm.
He built it in stages with Claude Code: starting on his phone with Opus 5.5, then switching to Fable 5.2 on his laptop once it was released, leaving Claude running and chatting with it while it iterated. The design leaned on a 2007 paper, BeepBeep, on acoustic ranging with ordinary devices. One mechanism is worth knowing about if you reuse the code. The listeners can receive and run new JavaScript sent from the server over the WebSocket. That is how the system was updated without touching each device — and it means the server can run arbitrary code on every listening device.
Limits
- One house, one repeating beep, a quiet room. The ~40 cm figure is Willison's result on his setup, not a general claim about locating sounds this way.
- The automatic device self-location did not work well. The rough mode — dragging icons to approximate positions by hand — was what made the map usable.
- The beep had a fixed frequency the system could listen for. A sound that changes pitch, or a room with steady background noise, is a harder problem than this one.
- The system gives a coding agent ears only in a narrow sense: Claude has no audio input of its own, and it works here by running code that analyses microphone audio.
Related playbooks
- The Claude Code email check got narrower in 2.1.321
- Claude Design closes December 14: export now
- Claude Duet: Anthropic's proactive agent app
- Claude reads your bank statements now — in the US
Sources
Back to: Everyday playbooks hub · Also: Claude designs three electronic prototypes