Guide
Legacy Windsurf Enterprise Prompt Credits Follow the Seat, Not the Person
On legacy credit-based Windsurf Enterprise contracts, a replacement inherits the seat's used prompt credits. Current self-serve quotas and newer Enterprise ACUs use different meters.
A new contractor can join a legacy Windsurf Enterprise seat and find part of the month’s prompt-credit grant already gone. That is documented behavior, but only for a narrow plan type.
The current Plans and Usage documentation, checked 28 August 2026, separates three systems: self-serve plans, newer Enterprise contracts billed in Agent Compute Units (ACUs), and legacy credit-based Enterprise. The seat-inheritance example appears only in the legacy credit section.
Do not apply it to Pro, Max, current Teams quotas, or an ACU contract.
The official 300-of-1,000 example
For legacy credit-based Enterprise, the documentation says prompt credits are allocated per seat at the start of each billing cycle. They belong to the seat, not to the person currently occupying it.
Its worked example uses a 50-seat plan. One member leaves after using 300 of 1,000 credits; the person who fills that seat starts with 700 for the rest of the billing period. The replacement may see a notice that the seat was previously used. The page says this is expected, and the seat returns to its standard allocation at the next cycle.
The numbers are an official illustration, not a promise that every Enterprise contract includes 1,000 credits. Contracted allocations vary.
What else the legacy-credit page confirms
- Prompt credits reset at the start of the next billing cycle and do not roll over.
- A premium-model message normally consumes one credit, but model multipliers can differ.
- An unsuccessful message does not consume a prompt credit.
- After the included prompt credits run out, available add-on credits are used.
- Legacy add-ons are pooled for the team and listed at $120 per 1,000 credits.
- Those add-ons do not expire while unused, but they require an active subscription to be spent; the balance becomes usable again after resubscription.
That price and mechanism live inside the legacy-credit documentation. Confirm the contract and admin billing page before purchasing, because newer Enterprise contracts use ACUs.
The public page does not say whether a brand-new mid-cycle Enterprise seat receives a full grant, a pro-rated grant, or no grant until the next cycle. Do not buy another seat on the assumption that it automatically creates a fresh 1,000-credit bucket.
Current self-serve plans are not credit seats
Windsurf is now presented as Devin Desktop. Its quota documentation says that in March 2026 the self-serve product replaced prompt credits with daily and weekly usage allowances. Free, Pro, Teams, and Max are described through quotas and, on eligible paid plans, extra usage at model API prices.
The current pricing page likewise describes refreshed allowances rather than a monthly 1,000-credit inheritance. Enterprise contracts continue under their own agreements; the Plans and Usage page says newer Enterprise plans are billed in contract-specific ACUs.
The account’s own label decides which section applies:
| Admin surface says | Use this operating model |
|---|---|
| Legacy prompt credits | A replacement inherits that seat’s used credits until cycle reset |
| ACUs | Follow the contract-specific ACU allocation; the public page does not repeat the inheritance example |
| Daily and weekly quota | The legacy seat-credit example does not apply |
One contrast with Cursor Teams
The people problem looks similar—one contractor leaves and another arrives—but the documented meters differ.
- Legacy Windsurf Enterprise: the replacement inherits the vacated seat’s existing prompt-credit usage.
- Cursor Teams: a removed member who used credits leaves the seat occupied until cycle end; a new member added mid-cycle is pro-rated. Cursor does not publicly explain every replacement-to-occupied-seat mapping.
See the Cursor Teams seat-removal guide for that separate invoice and refund rule. The Windsurf article is about remaining usage on one legacy seat, not Cursor’s future-invoice credit.
How to hand off a legacy credit seat
- Confirm the meter. Ask the admin whether the contract says legacy prompt credits or ACUs.
- Open Plan Info before the swap. Record the seat’s remaining credits and cycle-reset date.
- Tell the incoming person what they inherit. A low balance is not evidence that their own account consumed it.
- Use the contract, not the public example, for allocation. The 1,000-credit grant is illustrative.
- If the inherited balance is insufficient, ask the account team about add-ons and new-seat allocation. The public page confirms legacy pooled add-ons, but not the allocation of a new mid-cycle seat.
- Recheck after the cycle resets. The seat should return to the plan’s standard grant; an unexplained mismatch belongs in a support ticket.
The buy decision is therefore not “another person means another seat.” First determine whether the incoming person is sequentially taking a documented legacy seat, and how much of that seat’s grant remains. Buy additional capacity only after the admin page or account team shows what the contract will actually add.