發布日期：2026-07-17
現在你可以在 Windows 系統匣中即時看到最準確的 AI 使用額度，而且檢視歷史紀錄時介面也變得滑順無比。以前當 hook（掛鉤，特定事件發生時被觸發的小程式）傳回全新的 statusLine（顯示在終端機最底下的狀態列）資料時，系統匣卻常被備援的舊 cache（快取，把算過或查過的結果暫存起來直接用）覆蓋，導致顯示過期或錯誤的額度；現在系統匣會優先採用最新的掛鉤資料，並嚴格把關防範錯誤格式。同時，系統匣掃描歷史工作階段的頻率也加上了 30 秒的暫存限制，免去每次重新掃描所導致的卡頓。就像看銀行的臨櫃螢幕，以前網路一抖就顯示昨天餘額，而且每次刷新都重讀交易明細害螢幕死當；現在能鎖定即時餘額，明細也改為定期刷新，省電又順暢。
You can now see your most accurate AI quota right in the Windows tray, with history scans running completely lag-free. Previously, the tray could override a fresh statusLine payload with a stale .claude.json fallback cache if its timestamp seemed newer, displaying outdated or expired limits; the tray now always prioritizes complete live data and rejects malformed values. Additionally, history source scanning is now cached for 30 seconds instead of checking logs on every refresh tick, eliminating UI jank. It is like a bank screen that used to show yesterday's balance on a network glitch and froze because it re-read every transaction on every refresh; it now locks onto real-time balances and updates your statement list on a smart delay.
**The Windows tray no longer falls back to a stale quota cache when the hook already has live data**: a complete statusLine payload from the hook could still be overridden by the `.claude.json` fallback snapshot whenever its cached timestamp looked newer, even though that cache might describe a different or expired session; the tray now always prefers a complete hook payload, and the "complete" check itself is now stricter — malformed non-numeric percentages in the hook payload no longer count as complete, so a broken payload can't silently blank the quota by skipping the cache.
**Windows tray history scanning no longer re-scans every Codex/Claude session log on each refresh tick**: `history_source_scan()` results are now cached for 30 seconds, removing the main source of UI jank in the tray.