Skip to content

v0.2.0 - telemetry

Choose a tag to compare

@JLegends JLegends released this 21 Sep 15:39
· 3 commits to main since this release

Telemetry, so the pruning can be judged instead of assumed.

Savings alone cannot tell you whether the decisions are good, and the previous tokensSaved was a characters-per-token guess. This release adds the measurement that matters.

Metrics

  • rerunAfterDrop / rerunAfterTruncate — a tool call re-issued with the same tool and input under a new id, after the original was removed or shortened. That is the direct, measurable cost of a wrong decision.
  • tokensSaved now uses the same calibrated estimator as the threshold, instead of chars / 4.
  • Counters for transformCalls, engaged, belowThreshold, capReached, overflow, noKey, so "working well" is distinguishable from "never ran".
  • A per-session JSONL ledger (~/.local/share/opencode/jev-compaction-ledger.jsonl) with tokens before/after, dropped, truncated, requests, stage and re-runs, written only when a run actually changed something.

Reading it

If rerunAfterDrop climbs alongside dropped, the keep threshold is too high or Jev is being asked to judge content it cannot see. If dropped stays near zero while belowThreshold dominates, the plugin is dormant on your sessions and the trigger is higher than they ever reach.

See the Metrics section of the README for the file layout and field list.