Loading…
Registry / data
Where the agent directory comes from, and what we do and don't take from each source.
The first ~160 entries were imported from the publicly documented claw4science.org API (facts only: repo URLs, project names, categories). The import is historical — this directory is no longer synced from claw4science; categories and membership are curated here. Tags that originally came over with the import were later pruned to objective attributions only (see below).
14 academic bio-agents (single-cell annotation, omics analysis, therapeutic reasoning, protein design) were imported from the Awesome AI Meets Biology survey, with paper links pointing to peer-reviewed versions where they exist. Its sister collection Awesome AI Virtual Tumor contributed corrections to the same batch.
Stars, last-push time, language, license and repo descriptions are refreshed daily from the GitHub REST API for every listed repository. Licenses use the SPDX metadata GitHub reports; when it returns NOASSERTION, the repository's LICENSE file is read and standard Creative Commons titles are recognized. Freshness (active / stale) is derived from last-push time on a 120-day line. One unified verdict is applied at refresh: a repo with a peer-reviewed paper (journal or conference, any star count) or over 1000 stars with a preprint is judged stable; one archived by its owner or now 404 is judged gone; a repo idle past its tier's patience — 180 days under 30 stars, 1095 days at or above — is classified as archived. Everything except Stable is reversible.
Companion-paper metadata (title, venue, year, authors, DOI) is resolved through the awescholar CLI querying Semantic Scholar — one of the site's maintenance tools, alongside the GitHub API refresh. Enrichment starts from precise clues in the snapshot (DOI, arXiv ID, quoted title); agents without a resolvable clue are left untouched, and a weekly workflow retries the misses and commits what it resolves.
Category taxonomy, curation decisions and all editorial content are maintained by this project. Tags are objective attributions only — institution, publication venue, companion product and named technology (e.g. Stanford, Nature-Biotechnology) — never capability or marketing descriptors; those live in the category or the description. On the browse page, filter chips only surface institution tags that occur three or more times in the current view, so rare one-off attributions don't clutter the filters. Reviews are written by signed-in community members and are not copied from anywhere. AgentX is an independent community project, not affiliated with any source listed above or with any listed agent.
Every listing carries exactly one status. Only Stable and No repo are never rewritten by automation — Stable is sticky once granted, and No repo means there is no repository to track. The derived statuses Active, Stale, Archived and Gone are recomputed at each refresh and are reversible: a fresh push un-archives a record and a returning repository un-buries it.
| Active | Pushed within the last 120 days. | auto |
| Stale | No push for over 120 days — quiet, but the repo is still alive. | auto |
| Stable | Mature and feature-complete; quiet is expected. Granted automatically for a peer-reviewed companion paper (journal or conference) or a 1k+ star repo with a preprint, plus manual verdicts. Never revoked automatically. | auto + manual |
| Archived | Idle past its tier's patience — 180 days under 30 stars, 3 years above. A fresh push restores it. | auto |
| Gone | Code no longer usable on GitHub — deleted (404) or archived by its owner. Recovers if the repo returns. | auto |
| No repo | No GitHub repository, so freshness cannot be tracked. | manual |
The Nursery. Projects under 30 stars stay out of the default directory view — they are early-stage, and the main list stays signal-dominant. Find them behind the Nursery toggle on the browse page. A project graduates out of the watchlist when its stars reach 30 or it is judged Stable (regardless of stars), and is retired when it leaves GitHub for good (archived or gone) or has no repository to track. A nursery project idle for over 180 days is auto-archived at refresh. Retired records no longer appear in the directory or Nursery views — they move to the Graveyard page.
Recovery. Restores are fully automatic. A fresh push takes a record out of the archived state, and a repository that returns to GitHub comes back from the Gone state — both on the next refresh. Stable is the only status never revoked automatically; it is sticky once granted. Human corrections go through contribute.
Each listing belongs to exactly one category, answering one question: what does a user open this repository for?
See also the about page for how reviews work.