hotin — the whole field, ranked. With receipts.

hotin.ai

One command, one ranked list of what's actually hot in AI today: trending repos, models, papers and news, ranked daily by cross-source consensus. Numbers are receipts, badges are verdicts. Want the same thing in a browser? The live hotin board is what's trending in AI today, updated daily.

Every row shows why it is there: how fast it is growing, who backed it, where else it surfaced. Nothing ranks on a single source's say-so.

It works two ways, from one install.

Your model's training data has a cutoff and a web search returns marketing. Ask an agent what is worth using in AI this week and it guesses. Point it at hotin and it answers with the same ranked evidence you would have read yourself.

What it does

The zero-key core combines GitHub Trending, curated growth momentum, Hacker News, and npm velocity with no configuration. Add an optional key to unlock Reddit and YouTube (ScrapeCreators, or the official YouTube Data API v3), including curated repo-roundup channels. A “smart money” signal (repos the AI Insiders are backing) is included on a best-effort basis, and an AI-newsletter feed adds an editorial signal. Sources can be temporarily unavailable without taking down the CLI.

Beyond repos, hotin surfaces trending AI models (hotin models) and papers (hotin papers) as their own views, and a short daily hotin brief of what's happening across all of them. Run hotin refresh on a schedule and hotin records a time series, so the board can flag what's genuinely rising and viral (velocity, not just a snapshot) — not just what's big right now.

Install

pip install hotin

hotin has zero dependencies, so a plain pip install is safe (nothing to conflict with). Prefer an isolated install, or don't want to install at all?

uvx hotin              # run without installing (needs uv)
uv tool install hotin  # persistent command via uv
pipx install hotin     # persistent command via pipx
npx hotinai            # from the npm ecosystem (launcher; runs uvx/pipx under the hood)

No package manager, just Python? Grab the single-file hotin.pyz from the latest release and run it:

python hotin.pyz

Developing on a checkout: pip install -e ..

Use it from your AI agent (MCP)

The same board, callable by Claude Code, Cursor, Codex CLI, Gemini CLI, or anything else that speaks MCP. Pick whichever line is least work for you.

One click. Download hotin.mcpb and open it. Claude Desktop shows an install dialog and that is the whole process: no config file to find, no JSON to edit, no terminal. The bundle is 136 KB and carries hotin inside it, so there is nothing to install first -- hotin has zero dependencies, which is what makes that possible. macOS and Linux.

One line. Nothing installed at all, uvx fetches it on demand:

claude mcp add hotin -- uvx hotin mcp

Any other client. Same idea, as config:

{
  "mcpServers": {
    "hotin": { "command": "uvx", "args": ["hotin", "mcp"] }
  }
}

Already ran pip install hotin? Then it is "command": "hotin", "args": ["mcp"] -- the MCP server ships inside the package, there is no second thing to install.

Then ask your agent things it otherwise cannot answer:

"What AI repos are actually worth looking at this week?" "Is anything notable happening with open-weight models right now?" "Before we pick a library for this, what is trending and who is backing it?"

Two tools are exposed. hotin_board returns any tab (repos, rising, insiders, models, papers, news) with the receipts attached, and hotin_brief returns the daily digest. Answers come back in about a second, served from the local cache.

It runs on your machine, not ours. Your MCP client starts hotin as a local child process. It fetches GitHub, Hacker News, npm and Hugging Face directly, caches to your own disk, and uses your own token if you set one. hotin.ai is never in the path: the site is a separate rendering of the same tool, not a service this depends on.

Set GITHUB_TOKEN if you want the insiders signal; everything else works without any key. A first call on a cold cache takes about 15 seconds while it fetches; after that answers are served locally in about a second.

Works with every install route: the bundle, uvx, pip, pipx, and the single-file hotin.pyz.

Claude Code skill

skills/hotin/SKILL.md teaches an agent when to reach for the board and, more usefully, how to read it: which fields are actual evidence, and what the board does not know. Copy it in:

mkdir -p ~/.claude/skills && cp -R skills/hotin ~/.claude/skills/

It works with or without the MCP server, and is worth having alongside it — the MCP tool descriptions say what the tools return, the skill says which numbers mean something and when a row is a lead rather than a finding.

Quick start

hotin

Available commands:

Flags: --format text\|json\|md\|html · --limit N (default 20) · --source <name> (repos: one upstream feed instead of the fused board) · --since 30d / --min-stars N (repos filters) · --verbose.

Each repo result presents a score, the owner/repo (clickable), category, and applicable badges: fresh (recently created or active), rising / viral (climbing fast on the recorded time series, viral being the rare accelerating-and-consensus extreme), smart-money (the AI Insiders are backing it), and paper-backed (linked from a trending paper). Consensus across sources is folded into the score itself, not shown as a badge.

Example (real output, top of a live run):

$ hotin --limit 8
 30.59  xai-org/grok-build  agents  fresh
        Grok Build is open source
 22.17  justvugg/colibri  uncategorized
        Show HN: Getting GLM 5.2 running on my slow computer
 17.05  dietrichgebert/ponytail  app-building  fresh
 17.00  odysseus-dev/odysseus  uncategorized  fresh
 16.93  nexu-io/open-design  agents  fresh
 15.46  yuan1z0825/nature-skills  uncategorized  fresh
 15.24  bigpizzav3/codexplusplus  uncategorized  fresh
 14.77  antirez/ds4  inference  fresh

The first line of each result is score, owner/repo (clickable in a real terminal), category, and badges; a dimmed second line shows the human title when it adds context the slug doesn't. fresh reflects recent repository activity. In a live terminal the score and badges are colored. Your output will differ — it reflects what is actually hot when you run it.

Why corroboration, not popularity

Keeping it fresh