Claude Opus 5.5 made this.
Try this: Tap Shooting star, then try Long exposure.
Made by a Claude Code agent. It wrote the file in one go and never ran or fixed it.

Same prompt, other runs
Only one AI has run this prompt so far.
Receipt
- Made in
- Claude Code
- Paid with
- Claude subscription
- Time
- 13 min 23 s
- Tries
- Try 1 of 2
- Date
- Sep 30, 2026
- By
- a Claude Code agent
Made on a regular paid subscription, not the API.
Tries
- Try 1worksshownCode of try 1
- Try 2worksCode of try 2
How it was made
Each try was made the same way: a Claude Code subagent running Claude Opus 5.5 at high effort got only the prompt, pasted as is, and wrote index.html in a single step, without opening or testing it. Nobody edited the files.
Why there are two tries: on Oct 1, 2026 the build workflow restarted after a session limit and ran this prompt a second time, overwriting the first file. Before the site was published, its data listed only try 2, as if it were the only one. Try 1 was recovered byte for byte from the session logs on Nov 11, 2026.
- Try 1: Recovered byte for byte from the session logs on Nov 11, 2026. Checked that day in a headless browser: no console errors, renders on desktop and phone.
- Try 2: Accidental second try (the workflow restart).
How it was checked
- Console errors
- none
- Links and libraries
- all allowed
- Hands-free demo
- yes
- Phone check
- 390x844
- Libraries it loads
- none
What the AI says it built
I built a single index.html that draws the whole scene in one full-screen raw WebGL fragment shader. The aurora is ray-marched as three folding curtains with vertical rays, shifting from green to violet (and pink/red in storms). It reflects in patches of glassy ice between snow drifts. The scene also has a rotating star field with a long-exposure star-trail mode, shooting stars (automatic, or tap/click to send one across that spot), faint mountains, pine-ringed valley slopes and drifting mist. Controls cover Activity, Hue, drag-to-look, Long exposure, Shooting star, Restart, Hide and Mute. It has an FPS readout, an automatic resolution and quality scaler, synthesized Web Audio, a #demo mode with a visible pointer, and it sends the ready postMessage.
What it says it could not check
I never opened or ran the file, as the one-shot rules required, so a shader compile error or wrong visual balance (brightness, curtain placement, tree sizes) is possible. Star trails are drawn as arcs that grow over a few seconds rather than built up over real exposure time, and only the brighter star layer leaves trails. The faint stars just dim. Reflections are an approximation: a mirrored, half-quality version of the sky with some noise jitter, not a true blur. Tapping the ice sends a shooting star whose reflection crosses that spot. The pitch formula used to place the demo's lake tap ignores yaw. Audio starts on the first tap anywhere, and the keyboard shortcuts for looking around rely on dragging as their on-screen equivalent.
The benchmark
Aurora Over a Frozen Lake
A real-time shader aurora reflected in glassy lake ice.
I keep the exact prompts private for now.
Every AI on this benchmark