Highlights
- Reads local Claude state only when requested
- Useful for debugging and limit visibility
- Complements session and usage reports
Feature
Claude diagnostics
Inspect local Claude account state, cache freshness, and usage-data limit signals without external API access.
Intent
Feature
Focus
Claude diagnostics in vibestats is designed for developers who need more than totals and want to inspect local claude-specific state and limit clues.
Next step
Relevant commands
npx vibestats --claude-systemnpx vibestats --claude-limitsnpx vibestats limits claudeWhat claude diagnostics means
Claude diagnostics is about getting a clear, local view of AI coding activity without building custom spreadsheets or one-off scripts.
Who this is for
Developers who need more than totals and want to inspect local Claude-specific state and limit clues.
How vibestats handles it
vibestats includes Claude diagnostics commands that read local Claude files and present account, cache, and local limit context in a more usable format.
What you get back
You can debug confusing usage behavior, stale local state, or rate-limit questions without piecing together the file structure manually.
FAQ
Can vibestats help with claude diagnostics?
Yes. vibestats is built to support claude diagnostics with local reporting, aggregate pages, and command-line workflows.
Does this stay local?
Yes. vibestats is local-first. Prompts and responses stay out of the hosted pages unless you intentionally publish aggregate share output.
Where should I start?
Start with the command reference, then use the related links below to jump into wrapped reports, activity heatmaps, share pages, or diagnostics.
Related pages