#Issue with quota limit?

11 messages · Page 1 of 1 (latest)

real dawn
#

Hello!

I just discovered Warp and I’ve been using it for a few hours, I bought Pro after my 3rd hours of using the free plan,

Now it has passed roughly 15 hours and it say that I reached the quota limit? Is that technically possible? I would understand and have nothing against it if it would daily reset but monthly makes me think that I did something wrong or that something drains my ”tokens”?

Can someone clarify for me please,
PS I did read the thread about quota and token usage but a few hours of usage in my world shouldn’t maximize my plan within 5h of usage?

topaz roostBOT
#

Hi @real dawn. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

It's understandable to be surprised by hitting a quota limit so quickly after upgrading to Warp Pro. Based on the information in the knowledge sources, here’s what’s likely happening:

Warp AI usage is governed by two separate limits: the number of AI requests and the number of tokens used. Tokens are chunks of text (words, code, or characters) that the AI model processes. Each request consumes a certain number of tokens, depending on the length and complexity of your prompt and the AI's response. Even if you have requests left, you can still hit your monthly token limit, which will prevent further AI usage until your quota resets at the start of the next billing cycle. This is a common source of confusion, as the request counter and token counter are separate, and only the request count is typically visible in the UI right now [AI usage numbers in setting do not appear to match value used to limit requests].

It is technically possible to hit the token limit quickly if your prompts or the AI's responses are large, or if you use features like Agent mode, which can consume more tokens per request. Some users have reported hitting the token limit after only a few hours or a handful of complex queries, especially if the AI is processing large amounts of context or code [Token limit reached after 4 or 5 queries].

If you believe your usage was not excessive, it's possible that something in your workflow (such as large prompts, long responses, or repeated context) is consuming tokens faster than expected. Unfortunately, Warp currently does not provide a detailed token usage counter, which makes it hard to track exactly how your quota is being used [Need AI Request / Token counter].

#

If you think there may be an error or if you need more clarity, you can reach out to Warp support for help. They can review your account and provide more details about your token usage [Token limit for unlimited plans].

Summary:

  • Hitting the token limit quickly is possible, especially with large or complex queries.
  • Token usage is separate from request count and can be consumed rapidly.
  • There is currently no in-app token usage tracker.
  • For further clarification or if you suspect an error, contact Warp support.

Let me know if you need more details or help contacting support!

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@real dawn Kapa.ai is still learning and improving, please let me know how I did by reacting below.

real dawn
#

@topaz roost I was working on a script where warp itself used slot of emojie syntaxes making the script not work, having warp to fix its own problem it caused, I feel like shouldn’t be excessively paid by end user.

I believe there are a bunch of self inflicted issues espcially when activating auto apply recommended changes as it doesn’t do the job all at once but instead prompt itself sometimes 40 times in a row and I’d assume that is excessive and unessecary costly for me?

topaz roostBOT
#

Let me check the knowledge base for you again. One moment! :books:

#

You are correct in your observation—several users have reported that Warp's AI can sometimes get stuck in loops where it repeatedly tries to fix issues it introduced itself, such as inserting unnecessary emoji syntax or making repeated, incremental changes. This behavior can result in a rapid and excessive consumption of your monthly token quota, especially when using features like auto-apply or Agent Mode. Users have specifically noted that these self-inflicted loops can burn through tokens very quickly, sometimes without the user realizing it until they hit their quota limit [Need AI Request / Token counter], [WarpAI Duplicating and Repeating work and content in files].

Currently, there is no mechanism in Warp to prevent tokens from being consumed in these scenarios, nor is there a way to exclude self-correction loops from your quota. This has been a point of frustration for users, as it can lead to unexpectedly high token usage and costs, especially when the AI is not efficiently resolving the problem it created [Need AI Request / Token counter].

If you find this is happening frequently, you are not alone, and the Warp team is aware of the issue. Many users have requested more transparency and control over token usage, as well as improvements to prevent these costly loops. For now, the best approach is to monitor your usage closely and consider reaching out to Warp support to share your feedback and see if they can offer any assistance or workarounds.

#

In summary:

  • Yes, self-inflicted AI loops can rapidly consume your token quota and result in unnecessary costs.
  • There is currently no safeguard to prevent this, and it is a known issue.
  • User feedback is being collected, and improvements have been requested by the community.

If you need more control or transparency, you may want to upvote or comment on the related feature requests and bug reports to help prioritize this with the Warp team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:

#

@real dawn Kapa.ai is still learning and improving, please let me know how I did by reacting below.

real dawn
#

Could you forward me to support team to discuss this matter for a fair solution ? @topaz roost