Feature: prompt before consuming extra usage credits on session limit

Resolved 💬 2 comments Opened Apr 12, 2026 by biswasbiplob Closed May 23, 2026

Problem

In Enterprise/team organizations, when a user hits session limits, extra usage credits are consumed automatically with no prompt or confirmation. Users who have been allocated extra usage (e.g. $300) have no way to control when those credits get spent.

This means credits burn silently on routine work when the user would have preferred to wait for the limit reset and save the credits for higher-priority tasks.

Current behavior

  • User hits session limit
  • Extra usage credits are consumed automatically
  • No notification, no confirmation, no opt-in
  • Individual users cannot set their own spending controls — only org owners can

Requested behavior

When a user hits their session/usage limit:

  1. Show a clear notification that the limit has been reached
  2. Ask the user whether they want to continue using extra usage credits or pause and wait for the reset
  3. Let the user make this choice every time, without requiring org-owner intervention

This gives users agency over their allocated budget while still respecting org-level controls.

Why this matters

  • Users get allocated extra usage but have zero control over when it's spent
  • Automatic consumption defeats the purpose of budgeting credits for important work
  • The current workaround (asking the org owner to toggle spend limits on/off per user) is impractical
  • Anthropic support confirmed this is a gap in the current Enterprise design (conversation ID: 215473877573937)

Context

  • Affects Enterprise organization members using Claude Code
  • Support suggested filing as a feature request
  • The $0 spend limit workaround requires org-owner coordination for every usage decision, which doesn't scale

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗