claude-token-saver 2.14.1 → 2.14.2

package/bin/cli.js

@@ -24,7 +24,7 @@
 
 import { readFileSync } from 'node:fs';
 import { fileURLToPath } from 'node:url';
-import { dirname, join } from 'node:path';
+import { dirname, isAbsolute, join } from 'node:path';
 
 /**
  * Read the JSON blob Claude Code feeds the statusline command on stdin.
@@ -804,12 +804,16 @@ async function main() {
     process.stderr.write('Scanning session files...\n');
   }
 
-  // Exclude the current Claude Code session when computing lastActivity —
-  // otherwise the agent's own tool calls reset the countdown every few seconds.
+  // The current Claude Code session is only excluded from the lastActivity
+  // timer (so the agent's own tool calls don't reset the countdown). It MUST
+  // still feed ttlBreakdown — otherwise when the user's only recent traffic
+  // lives in the current session, the bucket signal collapses to empty and
+  // the statusline falsely flips to the 5m default. (See issue: Max users
+  // seeing "Cache expires 5:00" on idle even though their plan is 1h.)
   const excludeSessionPath =
     getArg('--exclude-session') || process.env.CACHE_MONITOR_EXCLUDE_SESSION || undefined;
 
-  const sessions = await parseAllSessions({ days, projectFilter, excludeSessionPath });
+  const sessions = await parseAllSessions({ days, projectFilter });
 
   if (sessions.length === 0) {
     // Statusline must always emit a single line (no multi-line help spam every 300ms)
@@ -913,10 +917,16 @@ async function main() {
   }
 
   // Last API activity feeds the statusline TTL countdown.
-  // For every session that wasn't excluded, take the full endTime (any API call
-  // keeps the prefix cache warm — it doesn't matter whether it's user- or
-  // agent-driven because the cache is shared across sessions by prefix content).
+  // For every session OTHER than the excluded (current) one, take the full
+  // endTime (any API call keeps the prefix cache warm — it doesn't matter
+  // whether it's user- or agent-driven because the cache is shared across
+  // sessions by prefix content). The current session is filtered here rather
+  // than at the parser, so its writes still inform ttlBreakdown above.
+  const excludeAbs = excludeSessionPath
+    ? (isAbsolute(excludeSessionPath) ? excludeSessionPath : join(process.cwd(), excludeSessionPath))
+    : null;
   const otherLastActivity = sessions
+    .filter((s) => !excludeAbs || s.filePath !== excludeAbs)
     .map((s) => (s.endTime ? s.endTime.getTime() : 0))
     .reduce((a, b) => Math.max(a, b), 0);
   // For the excluded (current) session, only the user's prompts count — the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-token-saver",
-  "version": "2.14.1",
+  "version": "2.14.2",
   "description": "Save tokens on Claude Code — spike diagnosis, 1M-context detection, TTL countdown, statusline. (formerly claude-cache-monitor)",
   "type": "module",
   "bin": {

package/src/formatters/statusline.js

@@ -158,9 +158,14 @@ export function formatReport(data, { color = true, verbose = false, timer = true
 
   // TTL dominance → color signal (1h = good, 5m = warning).
   // The subscription plan fixes this, so the bucket rarely changes — it's the countdown that matters.
-  const is1h = ttl.pct1h >= 0.5;
-  const bucketLabel = is1h ? '1h' : '5m';
-  const bucketColor = is1h ? GREEN : YELLOW;
+  // When ttl.total === 0 (no cache writes observed in the window), we cannot
+  // infer the bucket. Default to 1h-sized countdown rather than 5m so Max
+  // users on idle don't see a misleading "Cache expires 5:00". The bucket
+  // label is shown as "?" so the uncertainty is visible.
+  const hasTtlData = ttl.total > 0;
+  const is1h = hasTtlData ? ttl.pct1h >= 0.5 : true;
+  const bucketLabel = hasTtlData ? (is1h ? '1h' : '5m') : '?';
+  const bucketColor = hasTtlData ? (is1h ? GREEN : YELLOW) : GRAY;
   const ttlSeconds = is1h ? 3600 : 300;
 
   const savings = cost?.savings ?? 0;