claude-code - 💡(How to fix) Fix [Feature Request] Individual usage/token consumption visibility for Team plan users [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#50721Fetched 2026-04-20 12:14:54
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
0
Author
Timeline (top)
commented ×2labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

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

Problem Statement

Problem

Users on Claude for Teams plans have no way to view their own token consumption or usage history.

CommandResult
/usage"Only available for subscription plans" — misleading for paid team users
/cost"You are currently using your subscription to power your Claude Code usage" — no actionable data

Expected Behavior

Individual users should be able to see:

MetricDescription
Session usageToken consumption for the current session
Monthly usageCumulative token consumption for the current month
Usage historyHistorical trends over time

Why This Matters

ReasonDetails
Rate limit awarenessNo way to know you're approaching limits before hitting them
Productivity insightsUsage patterns help users work more efficiently
Regulated environmentsIn GxP / FDA 21 CFR Part 11 contexts, auditability is a compliance expectation
UX parityAPI pay-as-you-go users get better observability than paid subscription users

Proposed Solution

Suggested Solution

Re-enable /usage or /cost for team plan users with session and monthly token counts, or add a personal usage view under account settings at
claude.ai.

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Re-enable the /usage or /cost commands for team plan users to display session and monthly token counts, or add a personal usage view under account settings.

Guidance

  • Modify the existing /usage command to return token consumption data for team plan users, including session and monthly usage.
  • Consider adding a new command or flag to provide historical usage trends.
  • Update the account settings page at claude.ai to include a personal usage view for team plan users.
  • Ensure that the solution prioritizes rate limit awareness, productivity insights, and auditability for regulated environments.

Example

No code snippet is provided as the issue does not contain specific technical details about the implementation.

Notes

The solution should be designed with UX parity in mind, ensuring that paid subscription users have at least the same level of observability as API pay-as-you-go users.

Recommendation

Apply a workaround by re-enabling the /usage or /cost commands for team plan users, as this is a high-priority issue with significant impact on productivity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING