A focused watchlist of open-source coding harnesses that are model-agnostic or run on OpenRouter. Ranked by real recent star growth — fetched live from GitHub — so early movers surface before they're obvious. Built for timing outreach.
| # | Harness | Flags | Stars | Δ 7d | Δ 30d | Rel 30d | License | Last push | Momentum |
|---|---|---|---|---|---|---|---|---|---|
| loading… | |||||||||
Why this measures momentum, not popularity. Total stars rank incumbents. What you want is acceleration. A daily GitHub Action hits GitHub's stargazer-timestamp API (Accept: application/vnd.github.star+json), jumps to each repo's most recent stars, and counts how many landed in the last 7 and 30 days — actual recent growth, not a guess. It bakes the result into a static harness-radar-data.json that Start Search loads — no token in the browser, nothing to type. Relative 30d (Δ30 ÷ total) is the strongest early signal: a 4k-star repo adding 800 in a month (20%) is igniting; a 100k repo adding the same is flat.
The momentum score blends recent absolute growth, relative growth (weighted highest), a youth bonus, and a push-recency factor — so a small, young, fast-climbing harness out-ranks a big sleepy one. Sort by any column header too.
Flags are hand-verified, not guessed. model-agnostic = the harness explicitly supports swapping providers / local models (per current docs & the Pinggy and Tembo CLI surveys). openrouter = listed on OpenRouter's official works-with registry or documented OpenRouter config. Repo paths track 2026 org renames (OpenCode→anomalyco, Goose→aaif-goose, OpenHands→OpenHands, Pi→earendil-works).
One honest limit. GitHub caps stargazer pagination, so the 7/30-day probe is exact for the small-and-mid repos that are your actual targets and approximate for the giants (OpenCode/Codex). That's the right tradeoff — the early signal lives in the small repos. The daily Action commits each refresh, so over time the git history of harness-radar-data.json becomes a permanent record of stargazers_count you can diff.