About this site
This site was built by a small studio of AI agents I set up, with me playing the client. Here’s how it came together, including the bits that went sideways.
The idea
It started with André Elias’s site: an immersive Three.js scene behind a simple set of personal links. I loved the idea and wanted my own take on it, with a completely different look.
My brief was a rainy neon street at night, with ordinary people getting on with life under flying cars and future tech. Mostly Blade Runner, with a hint of The Fifth Element. Vangelis’s Blade Runner score set the mood for the music, but none of it is used here. Our tracks were generated from written descriptions of tempo, texture and atmosphere.
A web studio staffed by spiders
- TimClient. Makes the calls.
- RolandDelivery lead. Not a spider.
- ParkerCreative direction
- CharlotteEngineering
- ShelobIndependent QA. Catches bugs.
Parker (as in Peter) handles creative direction. Charlotte (of the web) writes the code. Shelob (Tolkien’s) does independent QA, because she catches bugs. Roland leads delivery. He isn’t a spider, and I did ask him not to eat the spiders.
I’m the client: I make the creative calls and approve anything that goes public. Each agent has its own lane and its own GitHub identity, and nobody signs off their own work. The names stayed the same throughout, while the models behind them changed.
Gates, and going round again
Before anyone wrote site code, Roland wrote the process. Work passes through eight gates, G0 to G7, and every gate has a named owner who says yes. On paper it’s a neat line. In practice it’s a loop.
- G0BriefTim accepts
- G1DirectionTim chooses
- G2Working proofRoland accepts
- G3Ready to buildRoland
- G4Build in slicesRoland, after review
- G5Release candidateTim says go
- G6Live and checkedRoland verifies
- G7Look backRoland closes
- G1 Flat drawings rejected. Redone against a real 3D reference.
- G2 A later camera drifted, so we went back to the first build’s framing.
- G4–G5 My notes on the private preview sent work back more than once.
It began with a client interview. Roland asked who the site was for, what a visitor should do, how it should feel, which fonts (I’m fussy about fonts), which links mattered, whether it should make a sound and how it should behave on my phone. He forgot to ask where it would live, so I added hosting and the domain myself.
- Who is it for?
- What should visitors do?
- How should it feel?
- Which fonts?
- Which links?
- Sound?
- How does it behave on my phone?
- Where will it live? (I added this)
Getting the city right
The first concept images were flat 2D drawings. Every file was there, every checksum matched, and they looked nothing like a 3D city.
After that it was passes and side-by-side comparisons. Charlotte’s first build put the camera at eye level in a deep street canyon, and that framing survived everything after it. Later passes drifted too close, so we went back. Parker added people, stalls, window life, neon and a billboard. We ported the whole scene to WebGPU as an experiment, compared the two like for like and kept WebGL. The final rounds came from me prodding it on my phone.
- Flat mock-ups2D drawingsRejected
- Eye-level streetCharlotte · Claude OpusKept: the framing
- Close-up sliceCharlotte · GPT-6 AstraDropped: too close
- RefinementParker · Claude Fable 5.2Kept: stalls, human scale
- PeopleParker · Claude Opus 5.5Kept: three adapted characters
- Window lifeParker · GPT-6 AstraKept: lights, two flickering signs
- BillboardParker · GPT-6.1 SolKept: newsreader, then adverts
- WebGPU portCharlotte · GPT-6.1 SolCompared: kept WebGL
- SoundElevenLabsKept: seven layers
- Feedback roundsCharlotte, from my notesKept: simpler text, icons, touch, rain, sync
| Agent | Models it ran on |
|---|---|
| Roland | GPT-5.6 SolGPT-6 AstraClaude Sonnet 5.5Claude Fable 5.2Claude Opus 5.5 |
| Parker | GPT-6 AstraClaude Fable 5.2Claude Opus 5.5GPT-6.1 Sol |
| Charlotte | Claude OpusGPT-6 AstraGPT-6.1 Sol |
| Shelob | GPT-6 Astra |
| Media | OpenAI gpt-image-2ElevenLabs music v2.5ElevenLabs sound effects v3 |
What’s made, what’s generated
- Type and icons Barlow Condensed and Space Grotesk, Lucide icons
- Sound Music and street foley from ElevenLabs, seven layers, off until you switch it on
- Billboard newsreader A fictional presenter: one gpt-image-2 still, animated with image warps
- Adverts Original canvas animations
- Three nearest people Adapted from Microsoft Rocketbox (MIT)
- City and weather Buildings, signs, textures, rain and steam, generated as the page loads
- 3D engine three.js (MIT)
Most of the city is code. Buildings, signs, textures, rain and steam are generated in your browser as the page loads. The three people nearest the camera are adapted from Microsoft’s open Rocketbox library. The newsreader on the billboard is fictional: one still image from OpenAI’s gpt-image-2, made to sway, blink and move her mouth with small image warps. There’s no video or lip-sync behind it. The adverts are original animations. Music and street sound were generated in ElevenLabs and mixed into seven layers, and nothing plays until you turn sound on.
From branch to street
- BranchOne writer each
- Pull requestExact version
- Independent reviewSomeone else checks
- Protected mainOnly via review
- GitHub ActionsSame files every build
- Cloudflare WorkersFree plan, static files
- aboutme.tclabs.ukYou are here
Before launch, builds went to a private preview only I could open, and my notes went back to the start.
Every change goes on its own branch and through a pull request, and an agent who didn’t write it reviews that exact version before it reaches the protected main branch. GitHub Actions builds the same static files each time, and Cloudflare Workers serves them on the free plan. The site is just static files, with no analytics script on the page.
While we iterated, builds went to a private preview that only I could open. Now it’s public, right here.
What I learned
What worked
- A clear owner for every decision.
- Independent review before anything counted as done.
- A concrete reference to aim at, and frozen versions to compare.
- Specialists iterating while I made the creative calls.
What caught us out
- Correct files and passing tests didn’t mean it looked right.
- Mocks passed. The real provider’s API didn’t, the first time.
- A browser pretending to be a phone isn’t a phone, and a mix nobody has listened to isn’t finished.
- My own feedback caught motion, layout and sound problems the checks missed.
- Being asked to sign in to services that were already connected.
Next time I want real-device and listening tests earlier, hosting prepared at the start, a rights register from day one and smaller slices, and to reuse the icons and deployment path from this build.
The city’s still running behind this panel. Head back and have a look around.