claude-code - 💡(How to fix) Fix Allow org users to view their own usage metrics [1 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#52033Fetched 2026-04-23 07:38:19
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Problem

Users with the claude_code_user role on organization plans have no way to check their own token consumption or usage metrics. The usage dashboard is only accessible to admins/primary owners.

Currently the only options are:

  • Ask an org admin to pull per-user metrics
  • /status shows session info but not monthly usage totals
  • ~/.claude.json has local counters but no token/cost data

Proposal

Expose a self-service usage view for individual org users — either via:

  • A CLI command (e.g., claude usage or /usage)
  • The claude.ai web UI (even for users with claude_code_user role)
  • An API endpoint scoped to the authenticated user's own data

Users should be able to see at minimum:

  • Token consumption (input/output) for the current billing period
  • Request counts
  • Model breakdown

Why

Org users have no visibility into how much of the org's budget they're consuming, and no way to self-regulate without constantly asking their admin. This is a common need for cost-conscious teams.

🤖 Generated with Claude Code

extent analysis

TL;DR

Exposing a self-service usage view for individual org users with the claude_code_user role could provide them with necessary visibility into their token consumption and usage metrics.

Guidance

  • To address the issue, consider adding a new CLI command (e.g., claude usage) or an API endpoint that allows users to view their own usage metrics, including token consumption and request counts.
  • The proposed solution should ensure that the usage data is scoped to the authenticated user's own information to maintain data privacy and security.
  • When designing the self-service usage view, consider including a model breakdown to provide users with a detailed understanding of their usage patterns.
  • It may be helpful to consult with the organization's admins and primary owners to determine the best approach for implementing this feature and ensuring it aligns with their existing workflows and security protocols.

Example

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

Notes

The proposed solution assumes that the necessary data is already being collected and stored, and that the primary challenge is providing a user-friendly interface for org users to access their own usage metrics.

Recommendation

Apply a workaround by implementing a self-service usage view for individual org users, as this would provide them with the necessary visibility into their token consumption and usage metrics, allowing for better cost management and self-regulation.

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

claude-code - 💡(How to fix) Fix Allow org users to view their own usage metrics [1 participants]