Does Composer 2.5 fall back to API usage after Auto + Composer reaches 0% on individual Pro?

Support Help
1

Hi Cursor team,

I’m on an individual Pro plan, and my usage page shows separate pools:

  • Auto + Composer
  • API

In the model picker, I can select Composer 2.5. When I use Composer 2.5, it appears to consume the Auto + Composer pool, not the API pool.

I’d like to clarify what happens after the Auto + Composer pool reaches 0%.

Questions:

  1. On an individual Pro plan, can Composer 2.5 continue to be used by consuming the API usage pool after Auto + Composer reaches 0%?
  2. Or is Composer 2.5 only available through the Auto + Composer pool, even if API usage remains?
  3. Is this behavior different between individual Pro and Team plans?
  4. Does this apply to all Composer models, such as Composer 2.5 and earlier versions?

The reason I’m asking is that the usage page shows API remaining separately, so it’s not obvious whether Composer can fall back to that pool.

Thanks!

5

Hey, thanks for the question. Point by point:

  1. Yes. You’re on the standard individual Pro plan with two pools (Auto + Composer and API). When you use Auto/Composer and the Auto + Composer pool runs out, usage spills over into your API quota. You can see this on the dashboard note: “Consumed by Auto. Additional usage consumes API quota.”

  2. That means Composer 2.5 isn’t locked to the Auto + Composer pool. If you still have API quota left, it’ll keep working from there. Spillover is one-way only, it won’t move usage back from API to Auto. One detail: if you explicitly pick a non-Auto named model, its usage is charged to the API quota right away, without touching the Auto pool.

  3. Yes, Team is different. Spillover is an individual-plan mechanic. On Team there’s a single shared pool instead of separate Auto and API pools with one-way spillover.

  4. About Composer models: when you use Composer family models through Auto/Composer, they go to the Auto + Composer pool and spill over the same way. The exact mapping depends on your current plan though, for example older plans with unlimited Auto can behave differently. Your dashboard is the source of truth since it says what each pool is consuming. For Composer 2.5 spillover specifically, I’d test it once after your Auto pool is exhausted to confirm it behaves the same on your plan.

Also, when both pools are exhausted (Auto + Composer and API) and usage-based pricing is off, requests just get blocked. Nothing extra will be charged.

Let me know if anything’s still unclear.

6

Thanks, that clarifies it. The distinction between the individual Pro spillover behavior and the Team shared pool is especially helpful. I appreciate the detailed explanation!