Thanks for helping improve ccost.
git clone https://github.com/peterxcli/ccost.git
cd ccost
cargo test
cargo run -- --helpTo try the TUI against your own logs:
cargo run -- --codex
cargo run -- --claude
cargo run -- --sessions /path/to/jsonl/sessionsGood starter areas include:
- Static README screenshots with sanitized data
- Benchmark scripts and reproducible benchmark numbers
- JSON or CSV export
- Additional log sources such as Cursor, OpenCode, Gemini CLI, or Goose
- Theme and color configuration
- Search-result copy-to-clipboard
- Keep changes focused.
- Add or update tests when parser, pricing, cache, search, or CLI behavior changes.
- Run
cargo testbefore opening a pull request. - Avoid committing personal session logs, prompts, file paths, stack traces, or secrets.
Session logs can contain sensitive prompts, code paths, stack traces, and secrets. Use synthetic or heavily sanitized fixtures in tests and screenshots.