[DOCS] `/cost` docs still say the command isn't relevant for subscribers
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/costs
Section/Topic
Using the /cost command on the costs page, plus the /cost row in the built-in commands reference
Current Documentation
No current code.claude.com page documents the new per-model or cache-hit breakdown in /cost for subscription users.
The costs guide currently says:
The/costcommand shows API token usage and is intended for API users. Claude Max and Pro subscribers have usage included in their subscription, so/costdata isn't relevant for billing purposes. Subscribers can use/statsto view usage patterns. The/costcommand provides detailed token usage statistics for your current session: Total cost: $0.55 Total duration (API): 6m 19.7s Total duration (wall): 6h 33m 10.2s Total code changes: 0 lines added, 0 lines removed
The commands reference currently says:
/cost | Show token usage statistics. See cost tracking guide for subscription-specific detailsWhat's Wrong or Missing?
A. The costs guide still describes /cost as not relevant for subscribers
Changelog v2.1.92 added:
Added per-model and cache-hit breakdown to /cost for subscription users
Current docs still tell subscribers that /cost is not relevant for them and send them to /stats instead. That guidance is now outdated if /cost includes subscription-user breakdowns.
B. The new subscriber-facing output is undocumented
The docs do not explain:
- that subscription users now get additional
/costoutput - what the per-model breakdown covers
- what the cache-hit breakdown represents
- how the subscription-user view relates to
/statsand to API billing-oriented/costdata
Suggested Improvement
Update the /cost documentation to distinguish API billing information from subscription-user analytics.
Specifically:
- revise the note so it no longer says
/costis irrelevant for subscribers - clarify which subscription plans receive the new breakdown
- document that subscription users can see per-model and cache-hit breakdowns in
/cost - add a subscriber-focused example or sample output showing the additional sections
- update the
/costrow in the commands reference so its “subscription-specific details” link points to actual documented subscriber behavior
Impact
Medium - Makes feature difficult to understand
Additional Context
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/costs | Primary /cost documentation currently says the command is intended for API users and not relevant for subscribers |
| https://code.claude.com/docs/en/commands | Built-in command table says /cost has subscription-specific details, but links to the outdated costs guidance |
Total scope: 2 pages affected
Source: Changelog v2.1.92
Exact changelog entry:
Added per-model and cache-hit breakdown to /cost for subscription usersShowing cached comments. Read the full discussion on GitHub ↗
4 Comments
I use Claude 2.1.92 with team plan subscription and get no breakdown if I call
/cost, it still shows:The changelog seems very misleading since it does not show anything, at least not for all subscription types.
Just checked the current docs again. This issue is not fully resolved yet.
Still relevant as of 2026-05-28. I checked the current docs and this documentation gap still appears unresolved.
Issue #43357 Verification
Title: [DOCS]
/costdocs still say the command isn't relevant for subscribersIssue Date: 2026-04-04
Verification Date: 2026-06-23
Status: RESOLVED
---
Issue Summary
This issue reports that the costs guide on https://code.claude.com/docs/en/costs still describes the
/costcommand as intended for API users and not relevant for subscribers, and that the new subscriber-facing per-model and cache-hit breakdown in/cost(added in changelog v2.1.92) is undocumented. The issue further notes that the/costrow in the built-in commands reference links to subscription-specific details that do not reflect the new behavior.---
Verification Results
Claim 1: The costs guide still describes
/costas not relevant for subscribersStatus: RESOLVED
The current
costspage no longer titles the relevant section "Using the /cost command." At https://code.claude.com/docs/en/costs, line 17 the section heading is now### Using the/usagecommand, and at lines 19-21 the Note states:The note is now scoped to the Session block within
/usage, not to the/costcommand itself. The introductory paragraph at line 9 still positions the page around API token consumption, and the paragraph at line 23 still scopes the dollar figure to the Session block. Thecostspage no longer tells subscribers to ignore/cost; instead it tells them to ignore the dollar figure in the Session block while keeping the rest of the screen.Verdict: The misleading "subscribers should not use /cost" guidance has been replaced. The same caveat is now correctly scoped to a specific sub-element of the merged
/usage//costview.---
Claim 2: The new subscriber-facing output in
/costis undocumentedStatus: RESOLVED
The current
costspage now documents the subscriber-facing breakdown. At https://code.claude.com/docs/en/costs, lines 32-34 state:The commands reference at https://code.claude.com/docs/en/commands reinforces the same description. At line 139 the
/usagerow reads:The implementation described in the live docs (breakdown by skill, subagent, plugin, and MCP server) differs in framing from the original v2.1.92 changelog text ("per-model and cache-hit breakdown"), but the new subscriber-facing output is explicitly documented on both the costs guide and the commands reference, including the eligible plans and how to switch between 24-hour and 7-day views.
Verdict: The new subscriber-facing output is documented in the costs guide and the commands reference, with the eligible plans, what the breakdown covers, and where to find it.
---
Claim 3: The
/costrow in the commands reference links to outdated subscription-specific detailsStatus: RESOLVED
At https://code.claude.com/docs/en/commands, line 66 the
/costrow now reads:The subscription-specific details that the old row pointed to have been replaced with a direct pointer to the merged
/usageview, which is now the page that documents the subscriber breakdown. Line 125 also lists/statsas "Alias for/usage. Opens on the Stats tab", keeping the three commands consistent.Verdict: The
/costrow no longer points at outdated subscription-specific guidance; it now redirects to the documented/usageview.---
Current State
| Claim | Status |
|-------|--------|
| The costs guide still describes
/costas not relevant for subscribers. | RESOLVED || The new subscriber-facing output in
/costis undocumented. | RESOLVED || The
/costrow in the commands reference links to outdated subscription-specific details. | RESOLVED |---
Suggested Fix
N/A - issue has been resolved.
---
References
/usagecommand", and the API-user caveat is scoped to the Session block within/usagerather than to/cost.d/wtoggle and VS Code parity noted./costis now listed as an alias for/usage./statsis listed as an alias for/usage, opening on the Stats tab./usagedescribes the session cost, plan usage limits, and activity stats, and notes the breakdown by skill, subagent, plugin, and MCP server for Pro, Max, Team, and Enterprise plans./costfor subscription users". The current docs describe a related but differently framed breakdown (by skill, subagent, plugin, and MCP server).---
Conclusion & Recommendation
Primary Concern: The issue reported that the costs guide still told subscribers that
/costwas not relevant for them and that the new subscriber-facing output added in v2.1.92 was undocumented.Resolution Status: RESOLVED
Recommendation: CLOSE
The costs guide now scopes the API-user caveat to the Session block within
/usage, and/costis an alias for/usagein the commands reference. The new subscriber-facing breakdown is documented in the costs guide and the commands reference, with the eligible plans and what the breakdown covers. The implementation described in the current docs differs in framing from the original v2.1.92 changelog wording, but the documentation gap the issue reported has been closed.