Reddit user u/Any-Reputation8118 posted a single-file, 61 KB WebGPU ocean to r/ClaudeAI in October, and it became one of the most widely shared AI graphics demos of the month. The creator says Claude Code and Opus 5.5 built it in about 30 minutes.
The demo renders waves simulated with a fast Fourier transform (FFT), whitecaps and a physically based sunset sky. Randy Olson's repost on X shows it running at about 260 fps at 1440p on an RTX 5070 Ti.
Reposts on X, including one by jurlycat, spread it further, and one of them reached about 853,000 views.
The detail worth copying is the method. The agent took screenshots of its own rendered output and used them to check its work, comparing what it saw with what it intended and fixing the problems it found.
Others quickly tried the same approach. tarasshyn built a 72 KB Moon and a 102 KB Mars.
SKatalystAI made a 52 KB rainy neon city and added a variation: a fresh "critic" agent reviewed the result three times, so the checking didn't rely only on the agent that wrote the code.
Why it matters: the visuals draw attention, but the feedback loop is the useful part. Agents struggle with visual work because they can't tell whether something looks right without seeing it. A screenshot-and-review loop is a cheap fix that works across engines, and the same idea of letting agents observe and test their work is behind most of the agent tooling released in October.
Caveat: the build time comes from the creator, and the performance and view figures come from reposts on X. AIGamer hasn't verified them.
How to try it: - Ask for one self-contained file, so the agent can see the whole program at once. - Give the agent a way to render and screenshot the output, and tell it to compare the screenshot with the brief after each change. - Bring in a separate critic agent with fresh context to review the output, rather than relying only on the agent that built it. - Set a performance target and have the agent measure it.
