Calibrate token accounting and Agent activity - #6
Merged
Conversation
Backtthefuture
marked this pull request as ready for review
July 19, 2026 23:23
canyexuanfan
added a commit
to canyexuanfan/TokenStep-Windows
that referenced
this pull request
Jul 31, 2026
镜像同步至 upstream HEAD a44b2e9（PR Backtthefuture#6 + Backtthefuture#7），包含： - 1b54e5c Calibrate token accounting and Agent activity · codexAccountingRevision=8 计量校准 · 新增 AgentWorkViews/DailyAgentWork 模型 · 实验来源采集器（ZCode/Hermes/WorkBuddy） · 节奏卡底部指标改版（Agent Token/近7日均） · tokenToolColor/orderedToolEntries 扩展 - 2f50c67 Recalculate stale accounting on launch · UsageSnapshotRefreshPolicy 启动自动校准 · DataService.requiresImmediateCodexRecalibration 后续将在 windows/ 目录用 Rust+JS 移植跨平台功能。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Lifecycle token events, compaction, child-Agent replay, and provider-specific cache semantics could inflate totals or present unknown cache coverage as a real zero. Cross-source proxy matching could also remove independent requests when only their timing and usage looked similar. The previous Agent card mixed unverifiable score/rank/work-time semantics.
Impact
Historical Codex totals may decrease after recalibration, but source logs are preserved. Cache hit rate appears only when coverage is complete. Cross-source records are deduplicated only with a shared request/response ID, or a shared session plus matching time/model/usage. Experimental Hermes/ZCode sources remain local-first and opt-in.
Validation