Skip to content

An archive · est. 2026

What they built.How they built it.In their words.

Every other AI directory tells you a tool exists. This one tells you what somebody made with it, what it cost, how long it took, and where they got stuck.

No sponsored placement. No auto-generated listings. Every record is researched by an editor from the project’s own repository, changelog, posts and interviews — and each one says where its facts came from.

Records filed
039
Builders
38
Tools indexed
35
Newest project
May 2026

Recent records

All 39 →
039classic-vibe-macWrite C in a browser tab, press Build & Run, and a System 7 Macintosh boots with your freshly compiled 68k application sitting on its desktop.Claude CodeMay 2026038VibeRaveA fork of Strudel that lets you hold a key, say a genre out loud, and have the music change on the next bar without the beat ever stopping.ClaudeApr 2026037Vibe Coding KeyboardA meme about vibe coding turned into working hardware: an ESP32-S3 desk keyboard with nine keys, a rotary encoder and a small screen holding ten switchable keymaps.Apr 2026036Clawd on DeskA pixel crab that sits on your desktop and shows what your AI coding agent is doing, so you can walk away from a long task.Claude CodeMar 2026035autoresearchGive an AI agent an LLM training script, a fixed five-minute budget and no supervision — then see what it found while you slept.Claude CodeCodexMar 2026034N.O.R.A.CoreA single-author AI companion with two brains, an encrypted diary of its own, and 98 commits signed in its own name.Claude CodeFeb 2026033AudioNoiseLinus Torvalds learning digital audio DSP by writing guitar effects — with the Python visualiser vibe-coded.Google AntigravityJan 2026

What is in a record

Six fields

01

The stack

Which editor, which model, which host. Named, not categorised — “Cursor plus Claude” is a different story from “Copilot”.

02

The build log

The stages in order, with the prompts that mattered. Copied verbatim where the builder kept them.

03

What it cost

Money and time. The two numbers that decide whether a reader attempts the same thing.

04

Where it broke

The dead ends. More useful than the success, and the part nobody publishes.

05

What they would redo

The builder’s own hindsight, recorded while it is still uncomfortable.

06

Proof it exists

A live URL or a public repo. No screenshots of things you cannot open.

Stack index

All 35 tools →

Open call

Built something with AI? The build log is worth more than the launch post.

Send a live URL or a public repo. We research the build story from what is already public — the repository, the commit history, the launch posts — then write the record and publish it with the builder credited. If you built it, say so and we will approach you before anything goes out. You keep every right to your own work.

Rejected on sight

  • A screenshot you cannot click through to
  • A thin wrapper around one chat API
  • An aggregator of other people’s projects
  • Anything the submitter does not own

We would rather turn a submission down than lower the bar. That is the point.