Repository navigation
v0.2.2 - telemetry and reporting
Telemetry plus the report that reads it. This is the first release that records whether a decision was a mistake, so a 0 here means "measured and fine", not "not measured".
What's measured
rerunAfterDrop/rerunAfterTruncate— a tool call re-issued with the same tool and input under a new id, after the original was removed or shortened. The direct, measurable cost of a wrong decision.tokensSavedfrom the same calibrated estimator as the threshold, notchars / 4.- Counters for
transformCalls,engaged,belowThreshold,capReached,overflow,noKey, so dormant is distinguishable from broken. - A per-session JSONL ledger, written only when a run changed something.
The report
npm run reportJoins the ledger to opencode's session records — neither half answers anything alone. Reports engagement, re-run rate with a verdict, pruned vs unpruned cohorts, before/after the install boundary, and the subagent cost share the sidebar widget surfaces.
It deliberately refuses to print a quality verdict when the installed plugin does not record re-runs. Before this, an old install produced "0% re-runs, judgement holding up" — which was the report lying, since a version that measures nothing also reports nothing.
Note
If you installed via a github: spec, the TUI half will not load: those installs land in a directory whose name contains a colon (github:owner/repo) and the TUI's module loading fails on it silently. Use the npm package.