[FEATURE] Show absolute token counts in /usage command

Preflight Checklist

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

Problem Statement

The /usage command currently only displays percentage-based information for token consumption (e.g., "31%").
While percentages are helpful for a quick overview, they don't provide the concrete numbers needed to
understand the actual scale of token usage. Users cannot tell if they've used 31,000 tokens out of 100,000 or
62,000 out of 200,000 without doing mental math or checking system logs.

Proposed Solution

Enhance the /usage command output to include absolute token counts alongside the percentage. For example:

Current output:
% of context used: 31%

Proposed output:
% of context used: 31% (62,213 / 200,000 tokens)

Or as a separate line:
% of context used: 31%
Tokens: 62,213 / 200,000

Alternative Solutions

Add a --verbose or --detailed flag to the /usage command that shows the absolute numbers when requested:
/usage --detailed

This approach keeps the default output clean while providing detailed information for users who need it.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

As a developer working on a complex task, I frequently check /usage to monitor my conversation budget. When I
see "31% used," I want to know:

• How many tokens have I actually consumed? (62,213)
• How many tokens do I have left? (137,787)
• Can I fit another large file read or API exploration? (yes, plenty of room)

With absolute numbers, I can make informed decisions about whether to:

• Continue with the current session
• Start a new conversation to preserve context
• Request a summary/compaction
• Load additional large files

This is particularly important when working with large codebases where token management directly impacts
productivity.

Additional Context

• Similar commands in other tools (like token counters in IDEs, API usage dashboards) typically show both

percentages and absolute numbers

• The system already tracks these exact numbers internally (visible in system reminders)
• This enhancement would align with user expectations from other token-aware tools
• Low implementation complexity since the data is already available