Repository navigation
Show also costs analysis #47
Description
Similiar to how ccusage is doing it, claude-code-log could also show the costs. It would be approximate, but nevertheless it gives a good indication for much each interaction did cost.
Similiar to how ccusage is doing it, claude-code-log could also show the costs. It would be approximate, but nevertheless it gives a good indication for much each interaction did cost.
Activity
daaain commentedon Dec 7, 2025
Hey @drummerwolli, I think it would be a cool feature, but I'm not sure if it's worth duplicating what ccusage is doing.
I guess since we're already aggregating token counts we could also use LiteLLM's cost calculation figures (which might be even easier as this is a Python library), but reading a bit ccusage's docs, there's quite a bit of complexity behind it if we want to do it the same depth.
The other option would be calling ccusage session --json or ccusage session --jq but that could add a fair bit of overhead as ccusage would do its own aggregation.
I'm currently working on an SQLite cache which could make this more viable as we'd only need to reprocess changed sessions.
cboos commentedon May 27, 2026
As we've started with plugins... this extra processing and additional decoration could be achieved via a plugin. We need to extend the surface of the plugins so that instead of replacing the existing formatting, they can complement it.