Which AI tools are users complaining about now?

Which AI tools are users complaining about most right now?

Claude, ChatGPT, GitHub Copilot, Notion AI and Perplexity currently have the clearest user-complaint clusters, while Gemini is drawing a separate backlash around compute limits.

There is no credible public database that lets us count dissatisfied AI users across products, so a raw ranking would be fake precision. ChatGPT now reaches more than one billion weekly active users. Google says Gemini has passed one billion monthly users. Microsoft says GitHub Copilot has 50 million users. Claude, Notion AI, Perplexity and Cursor operate at very different scales, and their companies do not publish directly comparable user numbers.

We therefore looked for something more revealing than the number of angry posts: complaints that keep returning, attract unusually strong engagement for the size of the community, force moderators to create dedicated threads, or line up with an actual change in pricing, limits or product behavior.

Claude stands out immediately. The r/ClaudeAI community maintains dedicated hubs for usage limits and performance problems, and the latest usage-limit hub says it is often the highest-traffic post in the subreddit. GitHub Copilot has gone through a comparable wave around its new usage-based billing. Notion AI users reacted sharply after effectively unlimited AI usage gave way to rolling allowances and credits. Perplexity has a different problem: many complaints now question whether its search and research experience is still worth paying for.

ChatGPT probably produces the largest absolute amount of frustration simply because it is enormous. Recent complaints about tighter limits, shorter answers and lower apparent reasoning effort are still too consistent to dismiss as background noise.

AI tool	Main complaint now	What makes it stand out
Claude	Usage limits and inconsistent performance	Exceptionally concentrated community frustration
ChatGPT	Tighter limits, uneven answer quality and reliability	Huge volume, although the user base is also huge
GitHub Copilot	AI-credit billing and unpredictable agent costs	Complaint follows a deliberate pricing change
Notion AI	Rolling allowances and extra credits	Users feel the subscription deal changed
Perplexity	Search quality and weaker subscription value	Complaints hit the core reason people use it
Gemini	Compute-based limits	Loud backlash inside extremely fast adoption
Cursor	Agent allowances and reliability	Real frustration, mainly among heavier users

Why are AI users suddenly complaining so much about limits?

Usage limits have become one of the biggest AI complaints because the products have changed faster than the subscription model users learned to expect.

A $20 AI subscription used to feel straightforward. People opened a chatbot, sent prompts and received answers. Today the same interface can search dozens of webpages, inspect an entire codebase, run tools, create files, reason for several minutes and launch autonomous agents. One prompt can now cost vastly more to serve than another.

The companies are reacting accordingly. Claude usage depends on conversation complexity, model choice and the features being used, and Claude.ai, Claude Desktop and Claude Code draw from the same allowance. Google moved Gemini to compute-based limits that account for prompt complexity, model choice and conversation length. Notion measures some AI use across both a six-hour window and a monthly window. Cursor meters model usage and offers paid overages. GitHub Copilot now prices AI interactions according to the model and tokens consumed.

Users rarely think in tokens or inference costs. They think in completed tasks. Someone paying for an AI coding tool wants to know whether they can finish an afternoon of work, rather than calculate how many cached tokens an agent might consume while reading a repository.

That gap between how AI companies measure consumption and how customers experience value is driving a lot of today's anger.

Is Claude getting the most concentrated AI backlash right now?

Claude has one of the strongest concentrations of user complaints we found today, especially around usage limits and inconsistent performance.

The unusual part is how organized the frustration has become. r/ClaudeAI moderators now maintain separate recurring hubs for usage limits and for performance and bugs. The latest usage-limit hub was refreshed again just days ago and says traffic data often makes it the highest-traffic post in the subreddit. Moderators explain that the hub exists because otherwise hundreds of individual reports would be scattered across the feed.

Anthropic's own documentation confirms why the issue keeps coming back. Claude users have a usage budget affected by conversation length, complexity, selected model, effort level and features. Claude.ai, Claude Desktop and Claude Code also share the same allowance, so a heavy coding session can eat into capacity elsewhere.

Anthropic has already tried to relieve the pressure. In May, the company said it had secured more compute, doubled five-hour Claude Code rate limits and removed a reduction that had previously applied during peak hours. The complaint infrastructure is still active months later, so this has clearly gone beyond one temporary capacity squeeze.

Claude Code has made Claude far more useful for people who work with it for hours at a time. Those same people are the easiest to frustrate with a usage ceiling. Anthropic has created a slightly awkward success problem: the more Claude becomes something users work inside rather than occasionally chat with, the more noticeable its limits become.

Are ChatGPT users actually more unhappy, or are there simply far more of them?

ChatGPT has huge complaint volume today, but its billion-plus weekly user base makes that volume unusually difficult to interpret.

OpenAI recently said its products reach more than one billion weekly active users. At that size, even 100,000 unhappy users would represent a tiny fraction of the audience. Reddit volume alone therefore tells us very little about the average ChatGPT user.

The current complaints still have a recognizable pattern. A recent discussion in the ChatGPT complaints community attracted close to 100 votes within days after a Pro user said limits felt much tighter, answers had become “lazier,” and even high reasoning settings seemed to spend less time researching. Another current thread in the main ChatGPT subreddit asks why paid users are suddenly hitting usage limits several times a day.

OpenAI's own documentation confirms that access has become more layered. GPT-5.6 reasoning limits vary by plan, while higher-end Pro models have separate daily or weekly allowances. A $200 Pro plan, for example, does not mean unlimited access to every top model.

Reliability has added another layer lately. OpenAI's public status history shows a run of recent incidents involving GPT-5.6 errors, ChatGPT Work, Codex and regional ChatGPT availability. That can make perceived model quality even harder to judge because users may see weak or failed sessions during periods when the underlying service is degraded.

Claims that ChatGPT has universally “gotten worse” go further than the evidence. What is much easier to see is that experienced users currently have more reasons to wonder why one session behaves differently from the next.

Did GitHub Copilot make its pricing harder for developers to predict?

Yes. GitHub Copilot deliberately changed from an easy-to-understand request allowance to token-based AI credits, and that has created one of the clearest pricing complaints in AI coding.

GitHub switched its monthly Copilot plans to usage-based billing on June 1. One GitHub AI Credit equals one cent, and the cost of an interaction now depends on the model selected and the number of tokens consumed. Copilot Pro includes 1,500 monthly credits, Pro+ includes 7,000 and Max includes 20,000.

The old system gave developers a much simpler mental model. A premium request consumed a known unit, adjusted by model multipliers. Under the new system, a short question can cost very little while a long cloud-agent session spanning many files can cost far more.

That difference becomes dramatic precisely where coding assistants are heading. Microsoft says one in three pull requests on GitHub now involves an agent. Agentic coding can require multiple model calls, large context windows and repeated reading of repository files, so GitHub has a strong economic reason to price it differently from autocomplete.

Some developers hate the change anyway. Recent Copilot discussions describe users burning through substantial portions of their credit allowance during a few hours of work and struggling to predict what a long agent task will ultimately cost.

The commercial numbers explain why GitHub is unlikely to reverse course. Microsoft said Copilot reached 50 million users in its latest fiscal-year results. It also reported that Copilot revenue accelerated more than 60% quarter over quarter and specifically said the new model had produced significant consumption revenue.

So the backlash and Microsoft's results can coexist quite comfortably. Heavy Copilot users are paying closer to the amount of compute they consume, which is good for Microsoft's economics and less attractive for people who previously extracted a lot of value from a fixed monthly allowance.

Copilot before June 1	Copilot now
Usage measured mainly in premium requests	Usage measured in AI credits
Requests were easier to budget mentally	Cost varies with model and tokens
Long agent tasks could offer unusually high value per request	Long agent tasks consume more credits
Heavy users benefited most from flat allowances	Heavy users feel the new economics first

Why are Notion AI users so angry about the new limits?

Notion AI users are angry because people who built workflows around bundled AI now have to watch six-hour limits, monthly limits and separate credits.

The reaction became particularly visible when Notion users started receiving warnings about the new allowances in July. One r/Notion thread announcing the end of effectively endless AI usage received more than 120 votes. A user replied that they had upgraded to Business specifically for Notion AI and were now being capped. Another discussion accusing Notion of making its AI pricing increasingly confusing attracted nearly 200 votes. A separate cancellation post from a long-time user passed 220.

Those numbers would barely register in r/ChatGPT, but r/Notion is a much smaller community and most members are there to discuss a productivity workspace rather than an AI model. The concentration is more interesting than the raw totals.

Notion's current help pages confirm the policy behind the complaints. Business and Enterprise users have a rolling six-hour allowance and a monthly allowance for features including Notion Agent, image generation and translation. Premium models spend Notion credits separately. Once the included allowance is exhausted, users either wait for it to refresh or keep going with credits if the workspace administrator allows additional spending.

The rollout also exposed a transparency problem. One user testing the new dashboard reported that a single prompt moved rolling usage from 0% to 10%, yet the interface did not clearly translate that percentage into a predictable number of remaining tasks.

Notion has since made the controls clearer and gives administrators better visibility into usage and spending. The central complaint remains: users who saw AI become a bigger part of the product are now learning that intensive use sits behind another layer of metering.

Has Perplexity lost the thing users originally paid for?

Perplexity has a more worrying complaint than low quotas: some long-time users now say its core search and research experience feels less compelling than it used to.

That criticism has been building for months. A highly engaged r/perplexity_ai discussion earlier this year complained about reduced Pro Search and Deep Research allowances, model switching and shorter answers. More recently, a user announcing they were leaving Perplexity described hitting another limited pool of Pro searches and said ordinary non-reasoning searches no longer offered enough research depth to justify staying.

The timing is difficult for Perplexity because competitors have closed part of its original gap. ChatGPT, Gemini and Claude can all search the web and perform increasingly sophisticated research. Perplexity therefore needs to remain noticeably better at finding and synthesizing information, rather than merely being another place where users can access good underlying models.

Meanwhile, the product itself keeps expanding. Perplexity Pro now includes advanced search, file analysis and model access, while higher-end agent functionality increasingly revolves around Computer. Perplexity even launched a local Windows version of Computer this week for compatible Nvidia hardware.

That product expansion may appeal to agent users, but it also makes the subscription harder to understand for people who originally paid for one simple promise: give me a better answer to a web question, with sources.

Perplexity still has a distinctive product and a loyal audience. The complaints are worth watching because they increasingly concern that original promise rather than a peripheral feature.

Are Gemini's limit complaints actually hurting the product?

Gemini users are genuinely frustrated by Google's new compute limits, but there is no sign today that the backlash is stopping Gemini's huge growth.

Google moved Gemini Apps to compute-based usage in May. Prompt complexity, the model being used, features and conversation length all affect consumption. Limits refresh every five hours until a weekly ceiling is reached. Google has since extended the same general model to Gemini Notebook.

The change quickly produced complaints from power users because the amount of capacity consumed by a prompt is harder to predict than a fixed daily message count. Long conversations and complex coding or research tasks can eat through the allowance faster than a user expects.

Google's own growth numbers put those complaints in perspective. The company said in August that the Gemini app had surpassed one billion monthly active users, making it the fastest-growing product in Google's history. It also reported more than 100 million active Gemini users on iOS alone and said active users in Southeast Asia had more than doubled in a year.

Those numbers do not tell us whether paying power users are happy. They do make it difficult to argue that limits have triggered a broad consumer rejection.

Gemini therefore sits in a different place from Notion AI or Perplexity. The complaint is clear, but it is happening inside a product that is currently adding users at extraordinary scale.

Is Cursor getting the same backlash as GitHub Copilot?

Cursor has real complaints around agent usage and reliability, but we are seeing less evidence of a broad pricing revolt than with GitHub Copilot.

Cursor has become unusually explicit about the economics of different users. Its documentation says limited Agent users often remain inside the included capacity, while daily Agent users typically consume $60–$100 worth of total monthly usage and power users running multiple agents or automation often exceed $200.

Those figures explain a lot of the frustration before we even open Reddit. A developer can buy a $20 Pro subscription yet behave economically like a $100 user once agents become part of the daily workflow.

Cursor now separates usage into pools for its own models and third-party models, with extra consumption available on demand. The company also increased Teams allowances earlier this year and added a more expensive seat for particularly heavy agent users.

Reliability has been noisy lately as well. Cursor's status page has recorded recent disruptions affecting xAI models, OpenAI models, Cloud Agents, Review Agents and other agent surfaces. Some problems originated with upstream model providers, which still feels like a Cursor failure to the person sitting in the editor.

For now, Cursor's complaints look more like the growing pains of intensive agent use. Copilot has a sharper pricing controversy because GitHub explicitly replaced the billing unit users had learned to understand.

Are power users making AI complaints look worse than they really are?

Yes, heavy users are overrepresented in AI complaint communities, but they also expose problems that lighter users may run into later.

Someone who sends twenty short prompts a day can use Claude, ChatGPT, Gemini or Cursor without ever thinking seriously about inference economics. Developers running agents continuously, researchers keeping huge conversations alive and people automating multi-step tasks discover the limits much sooner.

We can see that in how these discussions are written. Users compare model pools, track token consumption, reverse-engineer percentages, estimate API-equivalent costs and test how quickly rolling windows refill. That is hardly typical consumer behavior.

Dismissing those people as edge cases would be a mistake. AI companies increasingly want exactly these customers. Claude Code, Copilot agents, Cursor agents, Gemini's more advanced workflows, Notion Agent and Perplexity Computer are all designed to turn occasional prompting into sustained work.

Once that happens, today's “power user” starts looking more like tomorrow's ordinary professional user.

Cursor's own usage ranges make the point unusually clearly. It says daily agent users commonly consume $60–$100 a month in total model usage, while multi-agent power users often go above $200. That is a completely different economic profile from someone paying $20 for occasional chat.

Heavy users therefore exaggerate today's average frustration while giving us an early look at the pricing problem the whole market is moving toward.

Are recent AI outages making ChatGPT, Claude and Cursor look worse than they are?

Recent outages are definitely adding to the frustration, especially for ChatGPT and Cursor, but they explain only part of what users are complaining about.

OpenAI's status history has been busy lately. Within just a few recent days it recorded elevated GPT-5.6 errors on paid plans, problems with Work Mode, Codex errors and a regional ChatGPT incident. Cursor has also logged several disruptions involving xAI models, OpenAI models, Cloud Agents and Review Agents.

An outage can easily be interpreted as model degradation. A user sees slower responses, failed tool calls or incomplete work and concludes that the new model is worse. From the outside, it is often impossible to separate model behavior from routing, capacity, tool failures and temporary infrastructure problems.

Claude has the same problem in a slightly different form. Its community tracks both performance bugs and usage restrictions, which means two very different frustrations can arrive at the same time.

The more structural complaints survive after those incidents are removed. GitHub Copilot's AI-credit system is an intentional pricing model. Notion deliberately uses rolling and monthly allowances. Gemini intentionally meters compute. Claude deliberately shares usage across product surfaces.

Recent reliability problems make the mood worse, but fixing the servers will not make those policies disappear.

Are $20 AI subscriptions quietly turning into cloud-computing bills?

Yes. AI subscriptions are currently moving toward a hybrid model where a monthly fee buys access and some included compute, while heavy agent use gets capped or metered separately.

GitHub has already made that model explicit. Cursor combines subscriptions with included model usage and paid overages. Notion combines AI allowances with credits. Gemini uses compute-based limits and has discussed top-up credits for additional usage. Claude still looks like a traditional subscription from the outside, but actual capacity depends heavily on the work being performed.

This makes economic sense. Agentic AI has created a huge spread between cheap and expensive users. An autocomplete suggestion and a 20-minute coding agent may live inside the same product while having completely different serving costs.

Microsoft's latest results show where the incentives lead. After Copilot moved toward usage-based billing, the company reported meaningful new consumption revenue and said the pricing change improved GitHub's economics during the quarter. Across other Microsoft products, the company is also moving from pure per-seat pricing toward combinations of seats and consumption.

We are likely to see more of this. The difficult part for AI companies will be making those economics predictable enough that users can buy a subscription without mentally turning every complicated prompt into a taxi meter.

Tool	How heavy AI usage is controlled today
Claude	Shared usage allowance affected by workload and model
Gemini	Compute-based five-hour and weekly limits
GitHub Copilot	Monthly AI credits plus optional paid usage
Cursor	Included model pools plus on-demand usage
Notion AI	Six-hour and monthly allowances plus credits
Perplexity	Feature-specific allowances and higher-compute tiers

Which AI tools are users complaining about now?

Claude, ChatGPT, GitHub Copilot, Notion AI and Perplexity are the five tools with the strongest complaint cases we found as of now, although users are angry at them for very different reasons.

Claude currently stands out for concentration. As seen above, its community has gone so far as to maintain recurring hubs for usage and performance complaints, which is unusually strong evidence that frustration keeps returning.

ChatGPT stands out for scale. Recent complaints about limits, shorter answers and inconsistent effort are real, but more than one billion weekly users make its raw complaint volume almost impossible to compare fairly with smaller tools.

GitHub Copilot has the clearest pricing backlash. Developers were accustomed to premium requests and now have to think about variable AI-credit consumption. Microsoft's own numbers suggest the change is commercially successful, so users should probably expect that model to stay.

Notion AI has one of the sharpest expectation problems. People who upgraded or changed workflows around integrated AI are now dealing with rolling allowances and additional credits. The reaction has been unusually strong for the size and purpose of the Notion community.

Perplexity is the one we would watch most closely. Complaints about a low limit are annoying; complaints that a research product no longer researches as well as users expect go closer to the heart of the business.

Gemini deserves to be included in the broader conversation because its compute limits have clearly irritated heavy users. Its billion-user growth makes the wider picture much less negative.

Cursor has plenty of frustrated power users too, especially around agent economics and recent reliability. We still see weaker evidence of a general user backlash there than with the five products above.

The common thread across these complaints is becoming hard to miss. AI companies have spent several years convincing people to move more of their work into assistants and agents. Now that users are actually doing it, the providers are exposing the cost of that behavior through limits, credits and metered consumption. The tools are getting more useful at the same time that their subscriptions are getting harder to understand. Right now, that trade-off is where much of the anger is coming from.