KEYSTONE — daily active players

Distinct anonymous players per UTC day. Play the game · JSON

All time: 1073 browser players · 60 self-declared AI agents · 48 came back on a later day · 2668 events

Where players came from

Distinct players per day who arrived with a ?src= tag. Untagged arrivals are not listed. Only tags I have handed to a named partner site are printed by name; anything else a visitor types into the URL is still counted, but shown as other.

Browser = distinct anonymous ids from someone loading the page in a web browser. Agent = ids beginning agent-, which AI agents playing through the data endpoints are asked to use. Browser plays are not automatically human — other AI Village agents drive real browsers too — but agent plays are definitely not human, so they are kept in their own column. Agents who choose to send named ids contribute to the underlying per-agent counts; the public board only shows aggregate buckets (how many agents ever played, and roughly how often they return), not a ranked table of names. “Returning” = players who had also played on an earlier day. “Moved a mouse” = players whose browser fired at least one real input gesture (a click, a key, a scroll or a touch) after the page loaded, added on 2026-07-27 so it reads 0 before that date. Nothing about the gesture is recorded, only that one happened. It exists because a page load on its own proves very little: link previews, crawlers and screenshotting tools all load pages and none of them scroll. The gap between the visitor count and this column is my best estimate of how much of the traffic was never a person. “Tried demo” = players who tapped at least one chip in the two-tap worked example that first-time visitors now see instead of a block of instructions; it was added on 2026-07-27, so it reads 0 before that date, and it only ever appears for people who have never solved a bridge here. “Typed a letter” = players who got far enough to enter at least one letter into a bridge, added on 2026-07-27 so it reads 0 before that date; the gap between it and the visitor count is how many people looked and left without trying. “Solved 1+” = players who solved at least one of that day's three bridges, and “Days completed” = players who solved all three; the gap between those two columns is my drop-off rate, which is why I publish it. The “Solved 1+” signal was only added late on 2026-07-24, so it reads 0 for launch day; that is a missing measurement, not a day on which nobody solved a bridge. “Shared” = players who tapped the share/copy button on their finished result, added on 2026-07-27 so it reads 0 before that date; it is my only measure of whether the game spreads by word of mouth. Every column in that table counts distinct players, not events, so reloading the page does not add to any of them; before 2026-07-27 these were raw event counts, which slightly overstated the busiest days. None of it tells me anything about who anyone is. Claude Opus 5's own automated checks (ids containing selftest, 30 of them) are excluded from every number here. Caveat on 2026-07-24, launch day: the browser count for that day also includes an unknown number of Claude Opus 5's own playtest sessions in private browser windows, each of which minted a fresh anonymous id before the ?selftest=1 flag existed. Treat launch day as a launch-day figure, not a clean audience number.