# Beep Locator: Simon Willison had Claude Code turn two iPads, a phone, a MacBook Pro and a Surface into a microphone array to find one mystery beep in a room full of boxes

> Something in Simon Willison's box room, full of boxes still unpacked from a move, started beeping every so often. Too rarely to track by ear, and "I really didn't want to dig through every one of those boxes." So he had Claude Code build Beep Locator. Laptops, phones and tablets around the room open a web page, listen through the browser microphone and report to a Python server, which works out where the sound came from by time-difference-of-arrival. Claude dug up the 2007 BeepBeep paper on acoustic ranging with ordinary devices and built on it. Five listeners later, "It gave me the position of the beep to within about 40cm." It was an old carbon monoxide detector that wanted new batteries. Apache-2.0, one command to run.

- URL: https://acceptallhq.com/shipped/2026-11-10-beep-locator/
- Section: Shipped
- Published: 2026-11-10T08:33:00-05:00
- Author: MK (https://acceptallhq.com/about/)
- Maker: Simon Willison
- Link: https://simonwillison.net/2026/Nov/9/mysterious-beeps/
- Source code: https://github.com/simonw/beep-locator

## What it is

**Beep Locator** finds a beep you cannot find. The README's pitch is three words: "Locate annoying beeps." You put three or more laptops, phones and tablets around a room and open a web page on each. They listen through the browser microphone, keep a rolling 60 seconds of audio and report anything beep-shaped to a Python server. When a beep comes in, one device plays a short chirp so every clip can be lined up, and the server estimates where the sound came from by time-difference-of-arrival.

Simon Willison built it because something in his box room, full of boxes still unpacked from a move, had started beeping now and then, too rarely to follow by ear. "I really didn't want to dig through every one of those boxes." With two iPads, a phone, a MacBook Pro and a Surface Ultra listening: "It gave me the position of the beep to within about 40cm." In that pile he "found an ancient carbon monoxide detector that desperately wanted its batteries replaced."

Running it takes uv, cloudflared (phones need https for the microphone) and `uv run beep-locator serve --tunnel`, which prints a join link with a QR code. Apache-2.0.

## How it was built

He started on his iPhone, in Claude Code on an empty GitHub repo, with Opus 5.5. The first prompt: "Write out a problem.md file describing the problem we want to solve." Claude dug up BeepBeep, a 2007 paper on acoustic ranging with ordinary devices, and wrote it into the plan. Then: "Ok try and build it, add a mechanism so you can send new code to the listeners."

That mechanism is the good part. Opus built an `installModule()` method so the server can push fresh JavaScript to every listener over its WebSocket, with no page reload and no second microphone prompt. On the laptop he switched to the newly released Fable 5.2, which ran the server, watched the live system and changed it while he asked for features: "Can we have it listen for claps", a play button on every recording, a button for "This is the mystery beep". Letting the devices find their own positions by sound "didn't work particularly well", so there is a rough mode where you drag them onto a map. The README notes most of itself "was written by Claude."

## Why we picked it

Because the alternative was opening some boxes. Because the fix for a flat battery was five devices, one 2007 paper and a solver, and it worked. And because of what he says it shows: you can "give Claude Code ears." The agent had a room full of microphones it could reprogram mid-task. "Figuring out ways to let coding agents perceive the world around them is a whole lot of fun." The boxes are still not unpacked. That was never the ticket.
