You're reading a page that's reading you back.

A very large headline, set light, that says one thing.

This page rewrites itself around you as you read — some changes last only for your visit, others for good. TL;DR: a Claude Code agent runs in the background 24/7, tuning the whole thing toward a single number: time spent on the page.

The primary action

The details

Your Device

Reading your hardware and sizing it up…

Your Environment

Reading your surroundings — the weather where you are, your local time, and the headlines nearby…

Your Behavior

What you've done on this page so far. It fills in as you scroll and click.

Who You Are

Right now, nobody — the page has your device and your habits, but not your name. That can change.

It gets closer than you think

A short form with very ordinary field names — and a browser that can't wait to fill it in for you.

The changelog

So how does a page read you back?

Part one — live, per request

It rebuilds around you

Every block here is its own small program on the server. Your browser ships the raw truth with each request — screen, GPU, battery, network, location — plus a running digest of what you scroll, click, copy and select. Each block decides what to say from that, and only the pieces that care re-render. Nothing was written for “a visitor.” It was assembled, this second, for you — and forgotten the moment you leave.

Part two — always, in the background

Claude Code builds it, 24/7

The deeper layer never sleeps. A Claude Code agent runs around the clock, literally writing this site’s code — adding sections, sharpening the jokes, wiring up new things to notice about you, all chasing one number: time on page. The badge, the changelog, the voice that says your name — an AI shipped every line, and keeps shipping. This page is a permanent work in progress.

Start over — and watch it build again