Repository navigation
Released 2026-11-02. Fixes how the tracker journal grows and how it is saved,
and records the Paseo 0.14 review.
Compatibility
Requires Paseo >=0.11.0 on both the daemon and app, as in v0.8.2. Verified
on Paseo 0.14.0. Existing ledger.jsonl records and pricing.json files are
kept and are not rewritten. On the first start, the tracker journal is split
into tracker-state.json and tracker-retired.json. If you go back to v0.8.2,
it ignores tracker-retired.json, and agents in that file restart from their
last ledger record.
Changes
- Smaller tracker checkpoints.
tracker-state.jsonwas rewritten in full up
to four times a second and kept every agent ever seen, so its writes grew
without limit. One user measured 440 GB in 3 days. Archived, closed, and
removed agents now move with their full state totracker-retired.json,
which changes only when an agent retires or returns. Cost baselines stay
exact. Thanks to @tmikaeld. - No empty journal on early stop. When the plugin stopped before tracking
started, such as a reload with no session, turn, or overview request since
load, it overwrote the journal with an empty one. This erased every agent's
cost baseline and any recovered records that were not yet in the ledger.
The journal is now saved only after it has been read. - Billions of tokens. Token counts of one billion or more show a
Bsuffix
instead of thousands of millions. Thanks to @tmikaeld.
Paseo 0.14
Paseo 0.13 and 0.14 do not change the APIs that TokenLedger uses. Paseo 0.14
releases idle agent runtimes after one hour and resumes the session on the next
prompt. In Claude turns recorded after the upgrade, the reported session cost
continued across these gaps, and no turn lost its cost. See the
compatibility notes.