Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Commands docs still describe `/cost` and `/stats` as standalone commands after the `/usage` merge [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#52189•Fetched 2026-04-23 07:34:14
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/commands

Section/Topic

The commands table entries for /cost, /stats, and /usage, plus the /cost guidance in the cost tracking docs.

Current Documentation

The commands reference currently says:

| /cost | Show token usage statistics. See cost tracking guide for subscription-specific details | | /stats | Visualize daily usage, session history, streaks, and model preferences | | /usage | Show plan usage limits and rate limit status |

The cost tracking page also says:

The /cost command shows API token usage and is intended for API users. Claude Max and Pro subscribers have usage included in their subscription, so /cost data isn't relevant for billing purposes. Subscribers can use /stats to view usage patterns.

What's Wrong or Missing?

Changelog v2.1.118 says: Merged /costand/statsinto/usage — both remain as typing shortcuts that open the relevant tab.

The docs still present /cost, /stats, and /usage as three separate commands with separate purposes. They do not explain that /usage is now the unified command surface, and that typing /cost or /stats just opens the corresponding tab inside /usage.

That leaves the command reference and cost guidance outdated for users trying to understand which command is primary and what behavior to expect after v2.1.118.

Suggested Improvement

Update the commands reference to make /usage the primary documented command and describe /cost and /stats as typing shortcuts that open the Cost and Stats tabs within /usage.

Update the cost tracking page to match that model. For example, the subscriber note could explain that subscribers can open usage views through /usage, and that /stats remains a shortcut to the Stats tab rather than a separate standalone command.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageLine(s)Context
https://code.claude.com/docs/en/commands35, 83-94The commands table still documents /cost, /stats, and /usage as separate commands
https://code.claude.com/docs/en/costs17-23The cost tracking page still treats /cost and /stats as separate command surfaces

Total scope: 2 pages affected

Source: Changelog v2.1.118

Exact changelog entry: Merged /costand/statsinto/usage — both remain as typing shortcuts that open the relevant tab

extent analysis

TL;DR

Update the documentation to reflect that /usage is the primary command, with /cost and /stats as typing shortcuts to open specific tabs within /usage.

Guidance

  • Review the commands reference table at https://code.claude.com/docs/en/commands to ensure it accurately describes the current functionality of /cost, /stats, and /usage.
  • Update the cost tracking page at https://code.claude.com/docs/en/costs to explain that subscribers can access usage views through /usage and that /stats is a shortcut to the Stats tab.
  • Verify that the changes are consistent across the affected pages, including the commands table and the cost tracking page.
  • Consider adding a note to the documentation to clarify the change and provide context for users who may be familiar with the previous command structure.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The updates should be made to the specific lines mentioned in the Additional Context section of the issue: lines 35 and 83-94 on the commands page, and lines 17-23 on the cost tracking page.

Recommendation

Apply the suggested improvements to the documentation to ensure that it accurately reflects the current functionality of the commands and provides clear guidance for users. This will help to reduce confusion and make the feature easier to understand.

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…
#api#tokenizer error#prompt formatting#chain error#conversation history

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 [DOCS] Commands docs still describe `/cost` and `/stats` as standalone commands after the `/usage` merge [1 participants]