Coding harness usage signals

Explore public activity across eight source views, by source or by harness. Each keeps its own unit, time window, coverage, and limitations, so adoption context never becomes a quality score.

Explore usage
Source-separated rankings

Most used on OpenRouter

Traffic attributed to public coding apps using OpenRouter's app-attribution mechanism.

Token totals combine prompt and completion tokens. Tokenizers differ, attribution is opt-in, and this is not standardized work, users, or task success. Missing coverage means not mapped, never zero.

Download all signals (CSV)

Why these sources stay separate

OpenRouter tokens, Homebrew install events, package downloads, editor installs, and repository activity observe different populations. Adding them together would create a precise-looking but invalid total.

Routing
OpenRouter attributed tokens and requests over completed 1-day, 7-day, and 30-day UTC windows.
Distribution
Homebrew 30d events, npm last-month downloads, and cumulative downloads of explicitly matched stable GitHub release assets.
Editor marketplaces
Cumulative VS Code installs, Open VSX downloads, and JetBrains downloads for exact mapped extensions or plugins.
Repository interest
GitHub stars and forks for the repository already audited by HarnessMatch, with full, client, or support scope preserved.