← Back to all features

Token burn rate

Live consumption meters per session. Input/output split, cache hit rates. Watch your money evaporate in real time instead of finding out on the invoice.

SZ
WD
HC
🏠
Auth refactor ×
Claude 5h Codex 7h
JWT middleware rewritten
Token refresh added
src/types/auth.d.ts — updated

Running tests... 14 passed

git push origin feat/auth
Enumerating objects: 12, done.
Counting objects: 100% (12/12), done.
Writing objects: 100% (7/7), 2.14 KiB
Claude
Resets in
5h
0%3h 14m
7d
0%6d 11h
Codex
5h
0%4h 56m
7d
0%6d 23h

Session-level token visibility makes agent cost legible while work is still happening. That helps spot runaway prompts, bad loops, and waste before the bill arrives.

Because the data is attached to individual sessions, you can compare how different providers or tasks are behaving instead of relying on one aggregate number.

The point is practical control: enough detail to steer usage without turning cost tracking into a spreadsheet ritual.

Have a question about how this works in practice? Check the SlayZone FAQ or read about all features.

← Previous Dev servers, managed Next → The invoice prepper