Local CLI for analyzing Claude Code and other coding-agent token usage, costs, sessions, and billing-window activity from local usage data.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
78
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 16/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (5/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
5/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
No required blockers for this timeline preset.
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens.
Disclosure: editorial
bunx ccusageccusage is useful for developers who need local visibility into Claude Code and other coding-agent usage without building custom log parsers. It can summarize daily, weekly, monthly, and per-session usage, show Claude Code five-hour billing windows, export JSON, and provide a compact statusline-oriented view.
The fit for HeyClaude is strongest for teams that already use Claude Code heavily and want a fast way to understand token volume, cost trends, session shape, and project-level usage from local data.
Editorial listing. No paid placement or affiliate link is used.
Show that ccusage is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/tools/ccusage)ccusage side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Local CLI for analyzing Claude Code and other coding-agent token usage, costs, sessions, and billing-window activity from local usage data. Open dossier | Open-source status companion for Claude Code and Codex with live local session state, your-turn alerts, usage views, and native macOS and Windows applications. Open dossier | Open-source LLM observability platform for logging, metrics, cost tracking, feedback, and gateway workflows. Open dossier | Open-source project behind CodeLayer, an IDE for orchestrating AI coding agents built on Claude Code, with keyboard-first workflows, team context engineering, and parallel Claude Code sessions across worktrees and cloud workers. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | — | tristan666666 | — | JPette1783 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety · Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | tools | tools | tools | tools |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | ryoppippi | Tristan Tang | Helicone | HumanLayer |
| Added | 2026-06-02 | 2026-07-15 | 2026-04-27 | 2026-06-05 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Run from a trusted package source and review repository/package provenance before using in sensitive workspaces. Cost estimates depend on local usage data and pricing metadata; treat them as operational estimates, not billing authority. | ✓Agent Island reads local Claude Code and Codex session files to determine session state; review the requested filesystem access before use. The macOS release is ad-hoc signed rather than Apple-notarized, so first launch requires right-clicking the app and choosing Open. Windows packages are distributed through GitHub Releases, Scoop, and winget; verify the release source before installation. | — missing | ✓CodeLayer orchestrates AI coding agents that edit files and run commands in your repositories, so it inherits the execution risks of the underlying Claude Code agent. MultiClaude runs multiple Claude Code sessions in parallel across git worktrees; review changes per worktree before merging to avoid conflicting or unreviewed edits. Remote cloud workers can run agent sessions on external infrastructure; understand where code executes before enabling them. Scaling agent workflows to a whole team increases the blast radius of automated edits, so keep human review and branch protections in place. |
| Privacy notes | ✓Reads local coding-agent usage files from the developer machine to calculate token and cost reports. JSON export can include project or session metadata, so review output before sharing logs or reports publicly. | ✓Session monitoring is local and the project states that the app has no Agent Island account and no product telemetry. Usage views may call provider usage APIs with existing local credentials; those requests remain subject to the provider's privacy terms. Local transcript files and provider credentials can contain sensitive data and should not be included in public screenshots, issues, or logs. | ✓When used as a proxy, Helicone sits in the request path and logs your LLM prompts, responses, and metadata (Helicone cloud or your self-hosted instance); review what request data is captured, keep secrets out of logged payloads, or use the self-hosted/async logging options. | ✓Because it builds on Claude Code, repository code and context are sent to Anthropic's API to power the agent. Remote cloud workers process your code and context on external infrastructure; review the provider's terms before sending private code. Any API keys or credentials used by Claude Code and CodeLayer should be stored as secrets, not committed to source control. Team and context-engineering features can share prompts, context, and workflow data across collaborators, so avoid placing secrets in shared context. |
| Prerequisites | — none listed |
| — none listed |
|
| Install | | | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Monitor local Claude Code and Codex sessions from a native desktop companion and get notified when an agent needs your attention.
Source-backed guides for putting this to work.
Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.