Inspiration

As young people, we get most of our news from social media, and we’ve realized how easy it is to only ever hear one side. If you read about the same story on r/wallstreetbets and on r/technology, it can barely feel like the same event. Each subreddit has its own version, and if you stay in one long enough, that version starts to feel like the truth.

We found out this isn’t just our problem. A teammate’s mom who works as a consultant at McKinsey told us they’d tried to build something similar for their work, a way to see how different groups of people talk about the same topic online, but couldn’t get it working.

So we built r/eaction. You search a news event and see how every part of Reddit is reacting to it: which stories each community is telling, which communities agree with each other, and where the same people show up in different places.

What it does

r/eaction lets people explore public sentiment and opinion around any concept or event. Through our interface, users can search any topic and, within minutes, get a graphical map of the narratives surrounding it. We also provide features to analyze opinions over time and across communities, revealing which subreddits drive each narrative and how the conversation spreads between them.

How we built it

r/eaction runs on LangChain deepagents. An orchestrator agent plans the job and hands it off to 5 subagents, one at a time: search, clustering, narratives, timeline and the final briefing. Every run is traced in LangSmith, so you can see what each agent did and why.

Search: the search agent turns your query into Reddit searches through the Arctic Shift archive. An LLM judge scores the results for recall@k (how many of the top posts are actually about the event), and if coverage is thin, the agent searches again before downloading threads. Usernames are hashed before anything hits Supabase.

Narratives: each comment gets rewritten into a short claim, embedded with OpenAI, and clustered with UMAP + HDBSCAN. We cluster every community together instead of one subreddit at a time, so the same narrative gets recognized wherever it shows up. The agent also picks a stance axis that fits the event (0 to 1, e.g. “dangerous manipulator” vs “pitiable”) and checks that it actually splits the comments. If it doesn’t, the agent picks a new one and reruns it.

Connectivity: we compare communities three ways: which narratives they share, how many commenters they share, and who replies to whom. That’s how we tell an echo chamber apart from two communities actually arguing.

Time: the timeline agent finds where the conversation started, the phases it went through, and the turning points that shifted it.

Frontend: a map of communities colored by narrative or stance, a stream of the conversation over time, and a written briefing. Results get published to Supabase Storage, so past events load instantly. New searches run the agents live on our server.

Challenges we ran into

Picking the dataset took a lot of thought, since it decides what you can even find. We needed real communities, who replies to whom, and timestamps. Reddit was the only source with all three: subreddits are communities by design, threads show connections, and a public archive meant no API approval. Clustering each subreddit hid the important part: the same narrative showing up in very different communities. So we cluster everything together and measure how communities connect afterwards. Last was speed. Our search agent kept over-planning searches, and prompting it to do less wasn’t enough. We had to cap it in code.

Accomplishments that we're proud of

  1. Type any event, even one we’ve never seen, and the agents build a full narrative map in about 6 minutes. Search quality is measured. An LLM judge scores recall@k on every search, and the agent searches again if coverage is thin.
  2. The agents check their own work. In one run the stance axis didn’t split the comments, so the agent picked a new one and reran the analysis on its own.
  3. We compare communities three ways: shared narratives, shared commenters, and who replies to whom. That’s how we tell echo chambers from communities that argue.
  4. We found things we didn’t expect. On the Anthropic IPO, r/technology was the most bearish community. Jensen Huang’s story went from a joke to a scandal partway through.
  5. Thousands of comments across dozens of communities become a map, a timeline and a short briefing.
  6. Every run is traced in LangSmith, so you can see why the agents made each decision.

What we learned

  1. How you split the data decides what you can find.
  2. Agents work best with autonomy inside carefully set limits. Guardrails in code beat longer prompts every time.
  3. An agent that checks its own output, like our stance axis check, is worth more than one that runs a fixed pipeline.
  4. Getting the data is often the hardest and slowest part. Rate limits, timeouts and archive lag shaped our whole design more than the models did.

What's next for r/eaction

There is a lot of data that we were able to scrape that we didn’t know how to use. Getting user feedback from various users would be super helpful so that we can further cater to the people that would be using this. Potentially creating a version thats geared more towards researchers or journalists might be useful.

Additionally, the biggest issue that we ran into was trying to reduce the time it takes to complete the data scraping and clustering steps, given the amount of data we were dealing with. We hope to find ways to improve upon this area.

Built With

Share this project:

Updates

Submission history