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
148
Builders
144
Tools indexed
36
Newest project
Oct 2026

Recently talked about

-1,005 pts since the last scan · 1 new to the list

Ranked by points on Hacker News stories in the last 90 days. A story counts only when its link points at the project’s own repository or product site — matched by link, never by name.

  1. 1,665ptsCodex CLI14 stories · 719 comments · 2026-07-28“Codex Security” ↗
  2. 1,500ptsCursor32 stories · 873 comments · 2026-08-17“Cursor launches Origin, GitHub alternative” ↗
  3. 751ptsDeepSeek Harness3 stories · 315 comments · 2026-08-13“DeepSeek Harness developer preview” ↗
  4. 682ptsQM1 story · 163 comments · 2026-07-31“qm – Multiplayer agent harness for work” ↗
  5. 590ptsGrok Build1 story · 643 comments · 2026-07-15“Grok Build is open source” ↗
  6. 578ptsJeff2 stories · 231 comments · 2026-09-28“Jeff – Jev-compatible 0.8B decision models, trained at home, ~30 ms” ↗
  7. 570ptsMoonshine Voice1 story · 92 comments · 2026-07-14“Speech Recognition and TTS in less than 500kb” ↗
  8. 546ptsi-have-adhd3 stories · 371 comments · 2026-09-08“I-have-ADHD: A skill to stop coding agents from burying the answer” ↗

What it is, in one line

Every record in the archive, cut down to the one line that says what it is. 864 build-log stages are written up behind them. Click any of them.

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 36 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.