Token Usage
The Token Usage pillar tracks how many tokens a finished session costs. A session is “crushed” when the goal was reached and no rework was needed. Lower tokens per crushed session means you reached the same outcome with less spend.
Headline — Crush Weight
Section titled “Headline — Crush Weight”Median total tokens (input + output + cache reads + cache writes) per crushed session in the selected range. Median is used so one giant session can’t skew the number.
Crush Weight = median(total_tokens) over crushed sessionsSupporting numbers
Section titled “Supporting numbers”| Metric | What it tells you |
|---|---|
| TET | Token Efficiency Trend — this range ÷ prior range. Below 1.00 means cheaper than last time; above means more expensive. |
| TPT | Tokens Per Turn (input + output). A high TPT means each turn carries a lot of context — usually a sign you’re re-pasting code instead of using @file references. |
| $CPCS | Estimated cost per crushed session — Crush Weight × current model price. Rough estimate only. |
| Token mix | Where your tokens went across all sessions: input · output · cache read · cache write. |
What’s excluded
Section titled “What’s excluded”Sessions below the substance floor (no turns, no code change, no mutating tool calls) are routed to Trivia and do not feed Crush Weight. Sessions that failed the goal gate or hit rework still count toward TPT but are not part of the Crush Weight median.
Tight < 15K · Healthy 15–35K · Heavy 35–70K · Bloated 70K+ tokens per crushed session.