Teams error help!

Cursor version: 3.0.12
Operating system: Windows_NT x64 10.0.26200

Steps to reproduce:

  1. Login to Cursor Teams account
  2. Use a single PC environment
  3. Open multiple sheets/tabs within Cursor
  4. Execute AI requests across multiple sheets simultaneously or alternately
  5. Repeat several times (3–5 requests per sheet)
  6. After repeated usage, a sudden usage limit is triggered

Expected behavior:
Each sheet/tab should operate independently without triggering unexpected usage limits

Actual behavior:

  • Usage limit is suddenly reached when using multiple sheets on one PC
  • AI requests stop working due to limit restriction
  • Work becomes difficult in a multi-sheet environment

Additional context:

  • Issue occurs when multiple sheets are used simultaneously

  • Single sheet usage does not trig

    ger this issue

  • Not sure if this is caused by rate limiting, billing calculation, or a multi-session synchronization issue

  • Additional context:

    • This issue occurred at the beginning of the month with Usage confirmed at 0 before starting
    • Despite this, the limit was triggered after approximately 10 requests
    • Issue occurs when multiple sheets are used simultaneously
    • Single sheet usage does not trigger this issue
    • Not sure if this is caused by rate limiting, billing calculation, or a multi-session syn

Request ID:
Unable to capture (can provide if needed)

Hi @mover3166

This isn’t a bug — the usage limit is being triggered because of the model you’re using, combined with how billing works on your plan.

Your team is on the Teams plan with $20/member/month of included API usage. Usage is shared across all your tabs and windows — it’s tracked per user, not per tab. So opening multiple tabs doesn’t create separate usage pools.

The key factor here is model selection. You’re using claude-4.6-opus-high-thinking in Max Mode, which is one of the most expensive models available. A single Max Mode request with this model can consume several dollars of your usage budget due to the high per-token cost (especially for thinking/output tokens). At that rate, $20 of included usage can be exhausted in roughly 10-20 requests, which matches what you’re seeing.

A few options to get more out of your usage budget:

  • Use Auto mode for everyday tasks — it selects cost-effective models and draws from a separate, more generous usage pool

  • Use Max Mode selectively — reserve it for complex tasks that genuinely need the larger context window, as the Max Mode docs recommend

  • Enable on-demand usage — your team admin can set a spending limit to allow pay-as-you-go usage beyond the included $20

  • Try less expensive models — models like Gemini 3 Flash or Composer 2 cost significantly less per request

You can monitor your usage in real-time at cursor.com/dashboard under the Usage section. More details on how usage works: Usage and limits