Repository navigation
v0.8.0 — Paseo 0.12 background workspaces and accounting accuracy
TokenLedger v0.8.0
Released 2026-10-23. Tracks agents in Paseo 0.12 background workspaces and
makes token and cost accounting more accurate and more explicit about what is
unknown.
Compatibility
Requires Paseo >=0.11.0 on both the daemon and app, without an upper version
limit. The verified hosts are 0.11.1 and 0.12.0. SDK development
dependencies stay pinned to 0.11.1; CI checks 0.11.0, 0.11.1, 0.12.0, and the
latest SDK. See the compatibility notes.
Existing ledger.jsonl records are reinterpreted on read and are not
rewritten. Existing pricing.json files are kept. After updating, reload or
reopen the app so the client uses the new summary fields.
Changes
- Paseo 0.12 background workspaces. Paseo 0.12 hides background workspaces
from default agent and workspace lists. Before this release, turns in those
workspaces were closed as canceled with no usage. TokenLedger now requests
background workspaces, falls back on older hosts, and confirms a removal by
agent ID before it settles an open turn. - Overview ranges. Switching ranges stays on the same screen and no longer
adds a navigation entry per click. Thanks to @ChtJT (#4). - Usage scope. Per-turn usage is kept apart from OMP session/branch totals
and unknown-scope snapshots. Snapshots stay visible but are not added to turn
or date-range sums. - Unknown is not zero. Missing counts, cache rates, and costs show as
unknown. A cache hit rate shows only with a complete prompt denominator. The
panel, pill, sidebar, and overview mark incomplete usage and partial
estimates. - Pricing. No private price seeds or fixed currency conversion are built
in; new price files start empty. Prices match full model IDs and explicit
aliases. Ambiguous or formerly unsafe matches block reference fallback and
show a pricing.json warning.
Known gaps
Paseo 0.12.0 still omits cache-write counts and provider-internal subagent
usage. See usage API requirements.