Repository navigation
TokenLedger v0.6.3 — Paseo 0.10.2 compatibility
TokenLedger v0.6.3
Released 2026-09-30. Restores loading on Paseo 0.10.2 by removing the manifest's
<0.10.0 ceiling. The existing tracking implementation remains compatible;
token accounting, stored records, and custom prices are unchanged.
Compatibility policy
Requires Paseo >=0.9.1 on both the daemon and app, without an upper version
limit. A new Paseo version no longer disables TokenLedger solely because of
its version number. SDK dependencies remain pinned to 0.9.1.
Verified hosts are 0.9.1 and 0.10.2. Allowing later versions does not certify
untested releases; future restrictions will be based on confirmed incompatibilities.
CI now checks the minimum SDK, 0.10.2, and npm latest, including weekly runs.
See the compatibility policy and evidence.
Install or update
For an existing npm installation:
paseo plugin update token-ledgerFor an existing GitHub installation:
paseo plugin update token-ledger --ref v0.6.3For a new installation:
paseo plugin install npm:paseo-token-ledger
# or
paseo plugin add stv1024/token-ledger --ref v0.6.3Run paseo plugin ls; TokenLedger should be running. No ledger migration or
deletion is needed. Local development installations use
paseo plugin reload token-ledger.
Validation
- Typecheck and all 65 automated tests passed against the 0.9.1 and 0.10.2 SDKs.
- Reloaded successfully on the installed Paseo 0.10.2 daemon; client and server
bundles compiled and the plugin started without new errors. - Real Claude turns retained the session-cost baseline across a plugin reload.
A Codex turn retained and summed two request observations into one record. - The maintainer completed manual testing before authorizing release.
Paseo 0.10.2 still omits cache-write counts and Codex provider-internal child
usage from the public accounting API. This release does not recover that data.