ccusage VS /dev for Claude Code

• Easy to use CLI
  ccusage provides a simple command-line interface for analyzing Claude Code usage from local JSONL files, making it quick to get started without complex setup.
• Detailed cost breakdown
  It offers detailed reports on token usage and costs broken down by day, month, session, or billing blocks, helping users understand exactly where their usage and spending are going.
• No API key required
  Since it reads local usage data files directly rather than calling an API, it doesn't require additional API keys or credentials to generate reports.
• Open source and free
  ccusage is an open-source tool, allowing users to inspect, modify, and contribute to the codebase, and use it without licensing costs.
• Multiple output formats
  It supports various output formats including tables and JSON, making it flexible for both human review and integration into other scripts or dashboards.

Possible disadvantages

• Limited to Claude Code
  ccusage is specifically designed for analyzing Claude Code usage data, so it isn't useful for tracking usage of other AI tools or platforms.
• Depends on local data files
  The tool relies on local JSONL log files generated by Claude Code, so if those files are missing, corrupted, or in an unexpected format, the analysis may be incomplete or inaccurate.
• Requires Node.js environment
  Since it's a CLI tool typically run via Node.js or npm/npx, users need to have a compatible JavaScript runtime installed, which may be a barrier for non-developers.
• Manual updates needed
  As Claude Code's data format or features evolve, ccusage may require manual updates to stay compatible, and users need to keep the tool updated themselves.
• Limited visualization options
  The tool primarily focuses on text-based or tabular output, lacking built-in rich graphical visualizations that some users might want for deeper analysis.

• Skill-based architecture
  The project organizes Claude Code capabilities into modular 'skills' that can be individually managed, making it easier to extend and customize Claude Code's functionality for specific development tasks.
• Practical development focus
  The repository appears focused on practical developer workflows and skills, aiming to enhance Claude Code's usefulness for real-world software development scenarios rather than abstract capabilities.
• Open source and community-driven
  Being hosted on GitHub as an open-source project allows developers to contribute, fork, and adapt the skills to their own needs, fostering community collaboration and improvement.
• Structured skill definitions
  The project provides a structured way to define and document skills for Claude Code, which can help standardize how developers extend and share Claude Code capabilities.
• Low barrier to entry
  The repository offers a relatively straightforward approach for developers to get started with enhancing Claude Code, without requiring deep expertise in AI or complex setup procedures.

Possible disadvantages

• Limited maturity and adoption
  The project appears to be in early stages of development with limited community adoption, which means it may lack thorough testing, comprehensive documentation, and proven reliability in production environments.
• Sparse documentation
  The repository lacks detailed documentation, tutorials, and usage examples, making it challenging for new users to understand how to effectively use and contribute to the project.
• Uncertain maintenance
  As a relatively small and new project, there is no guarantee of long-term maintenance, regular updates, or timely bug fixes, which could be a risk for developers relying on it.
• Limited skill coverage
  The current set of skills available in the repository is limited and may not cover many common development scenarios, requiring users to create their own skills from scratch for their specific needs.
• Dependency on Claude Code ecosystem
  The project is tightly coupled to Claude Code's specific interface and behavior, meaning changes or updates to Claude Code could break compatibility and require significant rework of existing skills.

No analysis of ccusage yet.

• I built an AI usage tracker. Here are five alternatives, and why I took a different approach

  Ccusage reads local coding-agent logs and produces token and estimated-cost reports. Its documentation covers Claude Code, Codex and other supported CLIs, including JSON output, cache accounting and an offline mode using cached pricing.... - Source: dev.to / about 7 hours ago

• Mistral Large 4

  You can confirm the allowed usage amounts with something like [ccusage](https://ccusage.com/) or [tokscale](https://tokscale.ai/). - Source: Hacker News / 24 days ago

• tokenmaxxing: track AI coding usage across tools and devices

  Tokenmaxxing is our open-source CLI and public leaderboard for bringing those daily totals together. It builds on ccusage and syncs usage to one public profile. - Source: dev.to / 29 days ago

Tracking /dev for Claude Code since Jun 2026.