All use cases
For Founders, devtool teams, and builders choosing between tools.

Watch what people say about your product or a competitor

A competitor changed pricing. Or you did. You want to know how it landed, not in a month from a churn report but this week from the threads where people are actually deciding.

Free plan: 10 requests a day, no card.

Claude Code reddibee · connected
You

What are people saying about Cursor this week compared to last? Set a watch for complaints.

  1. product_pulse"Cursor", this week vs last 214 mentions · +60%
  2. search_discussionscomplaints, top thread per theme 3 themes
  3. watchescreate: Cursor, complaints, daily watch saved
Agent, via Reddibee
  • r/cursor New pricing wiped my usage in two days. Looking at alternatives.asks for alternative · permalink
  • X Cursor agent mode on a monorepo is genuinely good now. Ate my whole afternoon.recommendation · permalink
  • Hacker News Ask HN: Cursor vs Claude Code for a small team in 2026?asks for alternative · permalink

Read-only. Sources cited. Nothing posted.

How it goes today

An evening of tabs.

  • A keyword alert emails you every comment that contains your product name. Ninety percent are noise. You stop opening them.
  • You search Reddit by hand on the day a competitor changes pricing, scroll for an hour, and come away with vibes.
  • By the time the churn report shows the effect, the threads where people decided have been dead for a month.
With Reddibee

Three prompts.

  • Mentions split into complaints, people seeking an alternative, and recommendations, each bucket trended against last week.
  • The top five threads in each bucket with permalinks, so you read the ones that matter and skip the rest.
  • A watch that emails you new complaints every morning and is readable by your agent, so it can draft the reply.
Walkthrough

A real session, prompt by prompt.

Each step is one request. The whole session fits inside a Free day.

  1. 1

    Take the temperature

    The split tells you more than the volume. A spike in recommendations and a spike in complaints look the same in a keyword alert.

    You

    What are people saying about Cursor this week compared to last?

    Comes back

    214 mentions this week, up 60%. Complaints 41%, alternative-seeking 22%, recommendations 29%, the rest neutral. The jump is entirely in complaints, and it started on Tuesday.

  2. 2

    Read the complaints that cluster

    Sixty complaints are one problem, not sixty. You want the theme and one thread to read, not the firehose.

    You

    Group the complaints by theme and show me the top thread for each.

    Comes back

    Three themes: the pricing change (60% of complaints), usage limits being hit in a day, and a monorepo indexing regression. One representative thread per theme with score and permalink.

  3. 3

    Find the people already leaving

    This is the warmest list you will ever get: people publicly asking for what you sell, this week. Help them, do not pitch them.

    You

    Show me the alternative-seeking threads from the last 7 days, newest first, with what they are considering.

    Comes back

    Forty-seven threads. Claude Code named in 31, Windsurf in 12. Nine are from people who say they pay for a team plan. Each with a permalink.

  4. 4

    Set the watch

    The first check is manual. Every one after it should not be.

    You

    Watch Cursor for complaints and alternative-seeking. Email me new ones each morning.

    Comes back

    A watch saved to your key. New matches arrive as one email a day and as a resource your agent can read, so it can summarise or draft a reply before you have read the email.

Reading the answer

What the numbers mean.

You ask
What are people saying about Cursor this week compared to last? Set a watch for complaints.
You get
214 mentions this week, up 60% on last week. Complaints 41%, alternative-seeking 22%, recommendations 29%. Top five threads in each bucket, with permalinks. A watch now emails you new complaints every morning.

Compare the split, not the count

Volume rises when anything happens, good or bad. Read the complaint share first. Forty percent complaints on a normal week is the baseline for a popular tool; the same share on a quiet week is not.

Alternative-seeking is intent

A complaint is a feeling. "What are you switching to?" is a decision in progress. Weight that bucket far above the others when the product is a competitor, and treat it as an alarm when it is yours.

One thread per theme is enough

Reddibee returns the top thread per cluster on purpose. Reading ten variants of the same complaint teaches you nothing the first one did not. Spend the time on the reply instead.

Watch your own product and two competitors. The alternative-seeking bucket for a competitor is your warmest list of people to help.

Under the hood

The tools your agent picks.

You never call these by name. The agent reads the prompt and chooses. Listed so you know what is happening.

product_pulse
Mentions of a product over a window, classified into complaint, alternative-seeking, recommendation and neutral, trended against the previous window.
search_discussions
Full-text search across every source with filters for community, date, and classification.
watches
Saves a query against your key, runs it on a schedule, and delivers new matches by email and as an MCP resource.
get_thread
One thread with its comment tree, classified, so the agent can quote the exact objection.
Prompts to steal

Copy, swap the brackets, paste into your agent.

  • What are people saying about [product] this week compared to last? Split by complaint, alternative-seeking and recommendation.

  • Group this week’s complaints about [product] by theme. One representative thread each.

  • Show me people looking for an alternative to [competitor] in the last 7 days and what they are considering.

  • Which of the alternative-seeking threads mention what they currently pay? Quote it.

  • How did [competitor]’s pricing change land? Compare the 7 days before and after [date].

  • Watch [product] for complaints and alternative-seeking. Email me new matches every morning.

Where it falls short

Honest limits.

  • Reddibee classifies public threads. It does not track individual users, follow accounts, or build a profile of anyone. That is Reddit policy and ours.
  • Watches run on a schedule and batch matches into one email a day. If you need a ping within minutes of a post, a raw keyword alert is still the right tool for that.
  • Common words are hard. A product called "Linear" or "Notion" produces false positives that the classifier trims but does not eliminate. Add a qualifier to the prompt.
Questions

Asked before the first request.

How is this different from a keyword alert?

A keyword alert sends you every match. Reddibee tells you which matches are complaints, which are people about to switch, and which are praise, then trends each one. You read five threads instead of fifty emails.

Can I watch several products?

Yes. Free includes one watch, Starter ten, Pro unlimited. Most people watch their own product and two competitors.

Can my agent act on a watch?

Watches are readable as an MCP resource. Your agent can pull the new matches, summarise them, and draft a reply or a changelog note. Posting it is still up to you.

Does it cover comments or only posts?

Both. A complaint buried in the twentieth comment counts, and the permalink takes you to the comment, not the post.

Try it tonight.

10 requests a day, free. No card.