
A Raycast extension that provides real-time monitoring of Claude Code usage statistics using the ccusage CLI tool.
Monitor your Claude Code usage with comprehensive real-time statistics:

This extension requires the ccusage CLI tool to function properly. The extension automatically installs and runs ccusage using npx (Node Package Execute).
The Usage Limits feature is only available when Claude Code is authenticated with Claude OAuth.
Use Actions → Open Command Preferences when the extension is open. These section settings apply to the main command; the menu bar has its own settings.
If you encounter any issues or have suggestions, please create an issue in the repository.
The Raycast layout of this extension was inspired by the System Monitor extension.
Special thanks to @ryoppippi for creating the ccusage tool that makes this extension possible.
MIT
Monitor Claude Code usage with real-time tracking
Show Claude Code usage in menu bar
Update command subtitle with Claude Code usage data
npm_config_prefix to ~/.npm-global when that directory exists — pointing npm at a missing prefix made npx fail with ENOENT on nvm/Homebrew installs, breaking every commandget-usage-limits AI tool now show per-model windows alongside the 5-hour and 7-day totals. Previously these appeared only in the menu bar.limits array, so a window for any model shows up under its own name and period without an extension update. The older seven_day_sonnet and seven_day_opus fields still supply any window the array does not carry.{h}h{m}m, {M}m, {h.f}h, etc.●○), "Segmented" (▮▯), "Squares" (■□), "Diamonds" (◆◇), "Stars" (★☆), and "Braille" (⣿⣀) — shape-based tracks that render consistently whether a menu row is idle or selected, unlike the Solid style's shade track; the default is unchangedretry-after window, coordinates one backoff across the menu bar and main view, and shows the real wait time~/.claude/.credentials.json no longer shadows a fresh Keychain tokenccusage reports a session with no activity date (a non-Claude agent row, or one whose entries lack timestamps); the session shows "unknown" instead of failing the entire listccusage version and a redacted structural fingerprint of the output (field names and value types, never values), so version-specific schema drift is diagnosable from an error report aloneccusage reports usage from more than one coding agent (Claude, Codex, Gemini, etc.), the daily and weekly detail panels show the contributing agentsccusage v20's renamed row fields (period, nested metadata, session array)· instead of || so the separator no longer reads like a JavaScript operator▰▱ glyphs for cleaner, more uniform renderingRate Limits · Remaining or Rate Limits · Consumed█░), Blocks (▰▱), or ASCII (#-)extra_usage schema validation failing when used_credits or monthly_limit are nullseven_day_opus, seven_day_sonnet) failing Zod validation when API returns explicit null instead of omitting the fieldformatDuration no longer shows seconds alongside minutes (e.g. "4m" not "4m 43s")extractJSON helper to strip npx stdout noise (e.g. npm warnings) before parsing JSONnull resets_at valueget-usage-limits toonpx path resolution for XDG-based fnm installs by detecting fnm in both legacy ~/.fnm and ${XDG_DATA_HOME:-~/.local/share}/fnm locations{dailyCost} - Today's cost (e.g., "$1.23"){dailyTokens} - Today's total tokens (e.g., "2.34 MTok"){dailyInputTokens} - Today's input tokens{dailyOutputTokens} - Today's output tokens{dailyRatio} - Today's output/input token ratio (e.g., "1.23x"){monthlyCost} - This month's cost{monthlyTokens} - This month's total tokens{monthlyRatio} - This month's output/input token ratio{usageLimit} - 5-hour API usage limit percentage (e.g., "30%")~) expansion for home directory pathsget-usage-limits) for querying usage limits programmaticallycustomNpx preference was set, causing commands to not run properly.