The updater fetched GitHub metadata and rendered the dashboard payload in
a single step, so anything that published the site needed a GITHUB_TOKEN.
Cloudflare Pages builds from a Git webhook and has no business holding
one.
Split the tool into three modes. The default update step still fetches
GitHub and now records every API-sourced field in data/metadata.json,
which is committed alongside README.md and data/history.jsonl. The new
-build mode joins that snapshot with data/agents.yml and
data/history.jsonl to render dist/ with no network access and no token;
-check is unchanged.
Supporting changes:
- computeDeltaAt anchors the delta windows to when the data was fetched
rather than the wall clock, so a redeploy days later reproduces the
same Δ7d instead of sliding the window past its slack allowance.
- writeSiteData takes updatedAt explicitly for the same reason: the
timestamp labels data freshness, not build time.
- sortStats is extracted from fetchStats so the build step re-ranks
identically from committed metadata.
- An agents.yml entry with no metadata yet is omitted with a warning
instead of failing the build, which would otherwise block every deploy
between merging a new entry and the next nightly run.
- update.yml drops the GitHub Pages deploy steps and commits
data/metadata.json; ci.yml runs `go run . -build` so a build that would
break on deploy breaks in CI first.
- site/_headers stops the edge serving a stale data.json after a refresh.
- docs/DEPLOY.md covers the Cloudflare setup, including the one-time
bootstrap of data/metadata.json that the build depends on.
Also carries the in-progress curation work already in the tree: the
module rename to awesome-ai-dev-tools, retagged entries, and removal of
the archived Roo-Code, void, continue and suna entries.
"awesome-coding-agents" no longer described the contents once the scope
widened past coding agents to AI-powered developer tools generally. Renaming
now was near-free: 3 stars, 4 forks, 135 unique visitors, four months old.
Name selection avoided the crowded awesome-* namespace, where the obvious
candidates are held by established lists (awesome-ai-devtools 3.9k,
awesome-ai-tools 6.2k, awesome-ai-coding-tools 2.1k). "ai-dev-tools" has no
incumbent at the exact name.
- Repo renamed; GitHub description and homepage updated.
- Module path, User-Agent, .gitignore, H1, site <title>/og:title and every
GitHub Pages URL updated across README.md, templates/readme.tmpl,
docs/LOCAL_DEV.md and site/index.html.
- plans/reports/ left untouched: it is a dated historical record.
go build: ok. go run . -check: 43 agents valid. go test ./...: ok.
The list was already drifting past "coding agents" — ADEs were admitted in
the previous commit. Rather than keep widening criterion 1 one category at a
time, it now describes the actual subject: developer tools built around AI.
The dividing line becomes tools you use vs. building blocks you import, which
keeps libraries, SDKs, model weights and skill collections out.
The star floor drops from a soft "roughly 10,000+" to a hard 1,000:
- enforceStarFloor drops any below-floor entry from the ranking and emits an
::error:: annotation, so the published list can never violate the rule.
Dropping rather than failing keeps one bad entry from blocking the refresh
of every other repo.
- -check cannot catch this (star counts need the API, -check runs offline);
docs/CONTRIBUTING.md says so explicitly.
Side effect: Orkas (1,998 stars) now clears the floor it previously missed.
go run . -check: 43 agents valid. go test ./...: ok.
Criterion 1 previously excluded "workspaces for agents", which ruled out
the ADE category entirely. ADEs are the surface a developer actually works
in, the same way a coding agent is, so they now qualify on their own terms.
Libraries, SDKs, skill collections and observability-only layers stay out.
- Widen inclusion criterion 1 in templates/readme.tmpl and document the
two admitted kinds in docs/CONTRIBUTING.md.
- Add `orchestration` to the Workflow facet in validate.go so ADEs are
filterable as a distinct class on the dashboard.
- Add stablyai/orca (70.0k) and getpaseo/paseo (17.5k).
README.md is regenerated from the template by the daily run; its
Contributing section is updated here so it is not stale in the meantime.
go run . -check: 43 agents valid. go test ./...: ok.
A single category could not describe tools that ship as a CLI, an editor
plugin and a desktop app at once, and 7 of the 40 entries were filed
under a surface they only partly match — cline is "an SDK, IDE extension
or CLI assistant" in one `extension` slot, Reasonix ships CLI, desktop
and VS Code under `cli`, warp is a terminal filed as `ide`.
Tags cover five facets: surface (at least one), model access, workflow,
integration, and origin (at most one). tagVocabulary in validate.go is
the single source of truth — the validator, its error messages, and the
dashboard's filter chips all derive from it, the last via a new facets
field in site/data.json.
The dashboard now filters on tags with multi-select chips grouped by
facet: OR within a facet, AND across facets, plus a clear-filters
control, and search matches tags as well as name and description. Only
tags some row actually carries get a chip, so chips and rows cannot
disagree. Tag pills are tinted per facet, replacing the category badge.
All 40 entries are tagged from each repo's own README, topics and docs;
CONTRIBUTING documents every tag and the evidence rule for applying one.
A leftover `category:` key now fails validation with a message naming
its replacement, rather than being silently ignored.
README.md and data/history.jsonl are the regenerated updater output.
The maintenance criterion was unfalsifiable, so entries went years
without a push before anyone noticed by hand. The updater already
fetches pushedAt; warn when it is older than 90 days, alongside the
existing rename and archival annotations. Archived repos keep their own
warning rather than getting two.
Quantify the criterion in the README and CONTRIBUTING: dropped after 6
months idle, flagged past 3, with removal still a human decision.
Also correct two CONTRIBUTING claims the code contradicts — duplicates
are rejected by CI rather than ignored at run time, and renames do carry
history over once canonicalKeyMigrations has the old key.
- notes for gpt-engineer, void, Roo-Code (archived upstream) — shown
as badges + italics on the dashboard; kept for historical value
- README Contributing now states inclusion criteria: must BE a coding
agent (not tooling for agents), ~10k+ stars, open source + maintained
- resolves ambiguity for community PRs proposing sub-bar repos
- Add pi, OpenHands, warp, gpt-pilot, qwen-code, kilocode, onlook,
dyad, trae-agent, copilot-cli (19 -> 29 tracked repos)
- Update renamed slugs to canonical owners (anomalyco/opencode,
aaif-goose/goose, AntonOsika/gpt-engineer) with history key
migrations so star deltas survive the rename
- Generate site/data.json each run and deploy site/ (interactive
table + star-history chart) to GitHub Pages from the daily
workflow, since GITHUB_TOKEN bot pushes cannot trigger a separate
Pages workflow
Two new short docs unblock new contributors who currently have to read
the Go source to figure out the GITHUB_TOKEN requirement and the
agents.yml schema:
- docs/LOCAL_DEV.md walks through the PAT setup, the local run command,
what files the run modifies, and how to revert before opening a PR.
- docs/CONTRIBUTING.md documents the agents.yml fields, enumerates the
six valid category values, and explains the rename and deprecation
policy now that history is keyed canonically.
Also add a one-sentence caption under the table in readme.tmpl so the
Delta7d column has a definition in the rendered README.
Go updater that fetches AI agent coding tool repo stats via GitHub GraphQL
(batched, one query), sorts by star count, appends a daily snapshot to
data/history.jsonl, and regenerates README.md from templates/readme.tmpl.
Daily workflow at .github/workflows/update.yml refreshes rankings and
commits changes. Seed list in data/agents.yml covers 19 tracked repos.
tiennm99