[FEATURE] Pool and dynamically reallocate unused enterprise AI credits at month end

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Sep 15, 2026 · closed Sep 18, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Problem statement

Our enterprise subscription includes a monthly AI credit allowance per seat. In practice,
usage is highly skewed: most users consume a small fraction of their allocation while
power users exhaust theirs mid-project. Today, unused credits sit idle and are forfeited
at the start of the next billing cycle, so we pay for capacity that evaporates every month
end — while some users are blocked or forced into overage spend.

Proposed Solution

Proposed solution

Allow the organization to pool unused credits from under-utilized seats and make them
dynamically available to other users, with an emphasis on the final days of the cycle:

  1. Org-wide shared pool — unused included credits from all seats roll into one

organization-level pool instead of being forfeited per seat.

  1. Dynamic reallocation — when a user exceeds their personal allocation, they can

draw from the shared pool automatically (or via a simple admin-approved request).

  1. Month-end surplus window — in the final N days of the billing cycle, remaining

unused credits are surfaced as a clearly labeled "surplus" that any licensed user can
consume before reset.

  1. Visibility — admins and users can see: personal usage, pool remaining, and

projected month-end surplus (e.g., "You: 1,200 credits · Org pool: 42,000 remaining").

  1. Governance — optional per-team caps on pool draws, approval workflow for large

draws, and audit log of who consumed surplus credits.

Alternative solutions / current workarounds

  • Manually monitoring usage dashboards and telling power users to "save it for later" —

doesn't work; usage is unpredictable and the surplus still expires.

  • Buying additional paid credits up front — we'd be paying twice for the same capacity.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Use case example

  1. Enterprise with 100 seats, each with a monthly credit allowance.
  2. By day 25, ~80% of users have used <20% of their allocation; a few engineers are

blocked mid-project.

  1. With this feature, the ~60% of unused credits in the pool becomes available to the

blocked users on day 25–31.

  1. Result: near-zero forfeiture at month end, no mid-project blockages, no overage spend.

Additional Context

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗