Rendered at 08:14:35 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
gen220 2 days ago [-]
Really cool to see the difference in token usage across different harnesses.
These kind of independently-verified data points will be super important for companies (and individuals!) trying to measure RoI on token spend as they recover from letting people go wild on token usage in the past year.
stephensilber 2 days ago [-]
I have started using this to inspect some of my heavier sessions and it has helped uncover some of the parts of my workflow and my project's build pipeline that were really slowing me down.
I also had no idea how many cache misses were happening when I stepped away for an hour or more at times.
thehazarika 1 days ago [-]
Nice.I have been using codeburn but it only tells you spend not messages and everything else.
drschlachter 1 days ago [-]
Is there a way i can connect it to my profile and get an idea of my token use?
dpc94 19 hours ago [-]
There's a link to the repo at the bottom. It runs locally on your machine
modgate 2 minutes ago [-]
[flagged]
ixtli 2 days ago [-]
dug around in there briefly and the per-session explorer is the best part imo
TokenLat 2 hours ago [-]
[flagged]
joshstrange 2 days ago [-]
I can highly recommend https://agentsview.io/ for a way to dig into your LLM usage. It reads your local conversation files and provides a ton of visualizations as well as the ability to dig into each conversation and see all the tool calls/etc. It's incredibly powerful.
dpc94 2 days ago [-]
Looks interesting. One of the angles that I approached while building this was focusing on cache misses. Not sure if this shows much info about this category. My tool is also local only + detecting changes and syncing into a sqlite db
yeah i tried to do even deeper and classify the types of misses and their monetary cost. for example, I was using Fable at work, and a single TTL miss (responding an hour and half later), cost $6 for one message
These kind of independently-verified data points will be super important for companies (and individuals!) trying to measure RoI on token spend as they recover from letting people go wild on token usage in the past year.
I also had no idea how many cache misses were happening when I stepped away for an hour or more at times.
- https://cs.joshstrange.com/jzwC4Z9y
- https://cs.joshstrange.com/nynGc5V9