shipped / October 19, 2026
Five Hundred Clocks: Opus 5.5 ran its own subagents for 18 hours and built 500 clocks into one HTML file
score image files: 0
Tom Gally, a translator in Yokohama, tests new models by asking for clocks the way Simon Willison asks for pelicans. With Claude Opus 5.5 he got carried away. Over four sessions in the Claude chat interface, Claude wrote the spec, launched its own subagents to draw about 20 clocks each, tested them in a headless browser, sent the weak ones back and assembled 500 clocks into a single 6.3 MB HTML file with no images, fonts or libraries. Tom wrote the prompts and did not touch the code.
Built by Tom Gally with Claude Opus 5.5.
see the announcement on Hacker News →instructionsdemosource
What it is
Five Hundred Clocks is one HTML file, 6.3 MB, that tells the time 500 ways. A Roman siphon clepsydra drips a cup full every minute. A French Revolutionary dial runs ten decimal hours a day. Hours, minutes and seconds are knotted into an Inca quipu, written in balanced ternary on a Setun-style console, picked out in amber on a Penrose tiling, or lit up floor by floor in two tower blocks at night. Hover for the name and a line of explanation, click for the big view with "How to read it" and "How it works".
The toolbar lets you filter by category, search with /, pause, run the clocks at up to 3600Ă— and shift the time twelve hours either way. The README says the page loads no libraries, fonts, images or network requests. Every clock is drawn in JavaScript on a canvas, and the textures come from seeded noise. The sun and moon clocks guess your location from your time zone and never ask for it. The whole thing is CC0.
How it was built
Tom Gally is a translator, writer, teacher, lexicographer and musician in Yokohama. In the post he explains that he has been testing frontier models by having them build self-contained clock pages, his own riff on Simon Willison's pelican on a bicycle. Opus 5.5's clocks struck him as varied and polished, so he kept going: "Over the course of several sessions in the Claude chat interface, I had it build a total of 500 clocks."
The credit line at the top of the README is unusually exact: Claude Opus 5.5 wrote all the code and text. "Tom wrote the prompts, reviewed the results and decided what to keep; he did not write or edit the code." Asked on HN how much creative direction he gave, Tom answered "Almost nothing." His only instructions were to strive for variety, keep the page self-contained, randomize the order and put the names behind a hover.
The sessions ran on 15, 16 and 17 to 18 October, from 100 clocks to 240 to 380 to 500. In each one Claude wrote a specification and assignments, launched several subagents in parallel to write about 20 clocks each, reviewed the output, sent weak clocks back for revision and assembled the file. The final prompt reads "Work in orchestration mode: make the design decisions yourself without checking with me." Six builders took 55 to 76 minutes each; 14 of their 120 clocks went back for another pass. Every clock was tested in headless Chromium through Playwright for time jumps, midnight and noon crossings, fast-forward and pause, with contact sheets of snapshots checked by the orchestrating Claude.
The bill: about 18 hours and roughly 15 million tokens. "It used a big chunk of my Max subscription tokens for this week." The repo also ships the clock-kit, with the starter prompt, the orchestration playbook, the builder brief, the split and assemble tools, and about 165 ideas that never got built.
Why we picked it
Because the human job description was prompts, review and taste, and the result is a Roman water clock that siphons on the minute. Also because "make the design decisions yourself without checking with me" is the prompt we all type eventually, and this is what it looks like when it goes well. 165 unbuilt ideas. Someone's Max plan resets soon.
Shipped is Accept All's daily pick of things people build with AI, written by MK. We are not affiliated with Tom Gally; the work and the credit are theirs, so go tell them it's good. Newer: The Duck Pond: Claude tuned a duck synthesizer in a loop until a classifier rated it more duck than the real duck. Older: Dub Anything: a coding agent directs a film dub line by line, in the actors' own voices, on your own PC.