/last30days does one useful job Google still handles badly. Give it a topic, and it checks Reddit, X, YouTube, Hacker News and prediction markets for what people engaged with in the last month, then writes a short summary instead of handing you a pile of blue links to sort by yourself.
The free open-source project went from about 28,000 GitHub stars to more than 41,000 in roughly eight days in June 2026. Stars are only bookmarks from developers, so they don't prove quality. But that jump explains why people noticed it.
last30days star history, last30days README
What it pulls in
The tool first works out which subreddits, X accounts, YouTube channels and other sources fit your topic. Then it collects comments, videos, posts, code links and market odds, as long as you have the right logins or keys switched on.
It ranks those results by match, engagement and freshness. When the same story shows up in three places, it folds them into one entry instead of repeating itself. A Reddit thread with 1,500 upvotes becomes a stronger clue than a blog post nobody touched.
Where it beats search
A normal search is built to find pages. /last30days is built to find reaction. Useful. The README's example for a person's name pulls recent work, a new team, merged pull requests and a Reddit thread with 569 upvotes, not just an old profile page.
That helps before a meeting, a purchase, or an article, when you care less about the official page and more about what people are saying right now. It won't settle a fact. A wrong post with 5,000 likes can still outrank a right post with 50, so check the claims yourself. It is a quick map of the conversation, not a verdict. Use it that way.
Setup is the catch
/last30days is not a normal website you open in a browser. It is an Agent Skill for AI coding assistants, so you run it inside tools like Claude Code, Cursor or Gemini CLI. A hosted version at last30days.ai exists if you want the idea without a terminal.
Some sources work with no keys. Others need browser logins, helper tools or API keys. Scraping also breaks, and the commit history already shows fixes for sources that changed under it. It's worth the setup if you need a fast read on what people think now. It is a bad shortcut if you need a final answer.
