* feat: show reset time for 7-day usage in text-only mode
- When usageBarEnabled is false, 7d usage now displays reset time,
- consistent with the existing 5h usage text-only behavior.
* test: cover text-mode 7-day reset countdown
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix: resilient usage display under API rate limiting
The Anthropic usage API rate-limits to ~1 call per 5 minutes. With the
previous 60s cache TTL, 4 out of 5 API calls returned 429, causing the
HUD to permanently display "(429)" instead of actual usage data.
Three-layer fix:
- Increase cache TTL from 60s to 5 minutes to match rate limit window
- Preserve lastGoodData in cache across rate-limited periods so the HUD
always shows the best available data instead of errors
- Exponential backoff (60s→120s→240s→5min cap) with Retry-After header
support for consecutive 429 responses
Also show "syncing..." instead of raw HTTP status on first-run rate limit.
* Update usage-api.ts
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* fix: harden 429 cache fallback behavior
* test: stabilize usage cache suite after rebase
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix: treat zero-byte lock file as stale to prevent permanent busy state
If the HUD process crashes between fs.openSync(lockPath, 'wx') and
fs.writeFileSync(fd, timestamp), a 0-byte .usage-cache.lock remains.
readLockTimestamp() returns null for unparseable content, and the
existing guard (lockTimestamp != null && expired) never fires, leaving
the cache permanently stuck in 'busy' state.
Add a lockTimestamp === null guard that uses fs.statSync().mtimeMs to
distinguish a crash leftover (old mtime → remove and retry) from an
active writer that is between openSync and writeFileSync (recent mtime
→ return busy). The original != null stale-timestamp path is unchanged.
Closes#202
* test: stabilize stale-lock regression coverage
* test: make usage-api suite self-build for source-only PRs
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix: use version-based sorting instead of mtime for plugin selection
The statusline command used `ls -td` (sort by modification time) to
select the latest plugin version from the cache directory. When multiple
versions coexist after an upgrade, the older version can have a newer
mtime, causing the statusline to run the wrong version.
This led to a real issue where v0.0.7 (no proxy support) was selected
over v0.0.9, causing persistent 403 errors on the usage API for users
behind a required proxy.
Replace `ls -td | head -1` with `ls -d | sort -V | tail -1` to sort
by version number. Apply the equivalent fix for Windows PowerShell
using `[version]` casting.
Fixes#198
* docs: make setup version lookup portable
* docs: avoid login shell in setup command
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix(context): scale autocompact buffer by raw usage to avoid inflated percentages at low context
Previously the buffered context percentage applied a flat 22.5% buffer
regardless of actual usage. This caused the HUD to show ~28% context
used immediately after /clear or at session start, when real usage was
only ~5%. The fix scales the buffer linearly: zero buffer at ≤5% raw
usage, ramping to full buffer at ≥50%, matching when autocompact
actually kicks in.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
* test: harden autocompact buffer startup coverage
---------
Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* feat(config): add configurable usage cache TTL settings
Add cacheTtlSeconds and failureCacheTtlSeconds to the usage section of
config.json, allowing users to control how often the Anthropic usage API
is fetched (default 60s) and how quickly failures are retried (default 15s).
* docs: document usage cache TTL config options
* refactor(usage): bundle cache TTL params into single CacheTtls object
Replace cacheTtlMs/failureCacheTtlMs pair with a CacheTtls type wherever
they appear together, reducing parameter count in readCacheState, readCache,
waitForFreshCache, and UsageApiDeps.
* chore(build): drop dist changes from pr
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix(usage): skip API call when using custom provider
Check ANTHROPIC_BASE_URL / ANTHROPIC_API_BASE_URL env vars and skip
OAuth usage API call when user is configured to use a custom provider
(e.g., via cc-switch). This prevents unnecessary API failures when
the user is not using Anthropic's default endpoint.
* test(usage): add tests for custom API endpoint detection
Cover isUsingCustomApiEndpoint behavior via getUsage integration:
- ANTHROPIC_BASE_URL with custom endpoint returns null without fetch
- ANTHROPIC_API_BASE_URL with custom endpoint returns null without fetch
- Empty ANTHROPIC_BASE_URL proceeds normally (falsy check)
- Default endpoint with/without trailing slash proceeds normally
* docs: note that custom API endpoints skip usage display
* fix(usage): tighten custom endpoint detection
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
PR #174 (67ddceb) accidentally reverted the User-Agent from
'claude-code/2.1' back to 'claude-hud'. Anthropic's /api/oauth/usage
endpoint rejects non-official User-Agent strings with 429.
This was the root cause of issue #173 — not request volume or
failure cache TTL. Same token, same IP:
- User-Agent: claude-hud → 429 (always)
- User-Agent: claude-code/2.1 → 200 with usage data
Restores the fix from PR #168 (ceb1127).
Fixes#173
Co-authored-by: Peter Yan <yanxiaozerg1997@gmail.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix(usage-api): change User-Agent to avoid Anthropic 429 rate limiting
Anthropic applies stricter rate limits to non-official User-Agent
strings. The current 'claude-hud/1.0' consistently receives 429
responses while 'claude-code/2.1' succeeds for the same token.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test(usage-api): cover user-agent constant
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* feat(config): add showSessionName toggle (default off)
Session name display from #155 is now opt-in via display.showSessionName
config. This addresses user feedback requesting the ability to hide the
session name. Added to setup onboarding and configure command flows.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* test(docs): cover session-name default behavior
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix(usage-api): do not return socket from createConnection in proxy tunnel agent
Node.js _http_agent.js calls `oncreate(null, newSocket)` immediately
when createConnection returns a truthy value, which causes the HTTP
request to be written directly to the raw proxy socket before the
CONNECT handshake completes. Proxies like Clash reject this with
400 Bad Request, surfacing as persistent 403/network errors in the
Usage display.
Return undefined instead so the socket is only delivered via the
async callback after the CONNECT tunnel + TLS handshake succeeds.
Fixes proxy CONNECT failures with Clash and similar HTTP proxies.
* test(usage-api): cover proxy CONNECT request ordering
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* feat: add showProject config to hide project name from statusline
Adds `display.showProject` (default: true) to control whether the
project path is displayed. When set to false, the project name and
its associated git info are hidden from both compact and expanded
layouts.
* fix: keep git status visible when project name is hidden
---------
Co-authored-by: Jarrod Watts <jarrod@cubelabs.xyz>
* fix: consolidate CLAUDE_CONFIG_DIR handling and keychain fallback
* chore: remove dist artifacts from this PR
* chore: bump version to 0.0.8
* docs: expand 0.0.8 changelog from post-0.0.7 commits
