claude-usage-limits 1.5.0 → 1.5.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "usage-limits",
   "displayName": "Usage Limits",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Puts your remaining Claude Code usage limit into Claude's context before every prompt, so it opens with what fits in the budget instead of starting work that gets cut off. Reports headroom as turns rather than percentages, prices a job before you start it, and detects your plan tier.",
   "author": {
     "name": "Ridelink",

package/README.md

@@ -466,6 +466,12 @@ Good enough to plan with, not a bill. The honest caveats:
 - A rebuilt figure only counts what this machine did. If you also worked on
   another device it reads low, which is the dangerous direction, so treat it as
   a floor until you refresh.
+- If a rebuild comes out above a full window, it is refused rather than capped.
+  Local transcripts only see this machine, so a window mostly spent elsewhere
+  makes a point look far too cheap and any live spend divides to hundreds of
+  percent. Capping that at 100 would tell someone sitting at half their budget
+  that it was gone. The window is reported as unknown instead, with a nudge to
+  run `/usage`.
 
 [how-it-works.md](skills/usage-limits/references/how-it-works.md) has the field
 names, the formulas, and the rest of it.
@@ -491,7 +497,7 @@ test/                             node --test, no dependencies
 node --test
 ```
 
-157 tests over the pricing, the window arithmetic, plan and credit detection,
+164 tests over the pricing, the window arithmetic, plan and credit detection,
 the status line, the before-prompt line, job forecasting, per-project
 attribution, the CLI, packaging, and the settings save/restore.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-usage-limits",
-  "version": "1.5.0",
+  "version": "1.5.1",
   "description": "Puts your remaining Claude Code usage limit into Claude's context before every prompt, so it opens with what fits in the budget instead of starting work that gets cut off. Reports headroom as turns rather than percentages, prices a job before you start it, and detects your plan tier.",
   "keywords": [
     "claude",

package/skills/usage-limits/scripts/brief.js

@@ -237,6 +237,14 @@ function briefText(parts) {
       'That figure was rebuilt from local history because the ' +
         'snapshot is ' + parts.snapshotAge + ' old; run /usage to refresh it.'
     );
+  } else if (parts.staleWindows) {
+    // Do not quietly carry on with a window we know is wrong and could not
+    // rebuild. Say it is unknown and point at the one command that fixes it.
+    sentences.push(
+      'A window is past its reset and could not be rebuilt from local history, ' +
+        'so its reading is unknown rather than current; the snapshot is ' +
+        parts.snapshotAge + ' old, so run /usage before trusting the rest.'
+    );
   }
   if (parts.othersSummary) sentences.push('Other windows: ' + parts.othersSummary + '.');
   if (parts.session) {
@@ -290,6 +298,7 @@ async function run(now, hookInput) {
       session: sessionSpend(events, sessionId),
       othersSummary: summariseOthers(windows, binding && binding.key),
       sessions: usage.activeSessions(events, now, usage.CONCURRENT_WINDOW_MS),
+      staleWindows: windows.filter((w) => w.stale).length,
       binding: binding
         ? {
             key: binding.key,
@@ -324,6 +333,7 @@ async function run(now, hookInput) {
         : null,
     session: view.session,
     rebuilt: Boolean(binding && binding.estimated),
+    staleWindows: view.staleWindows || 0,
     snapshotAge: usage.formatDuration(base.snapshotAgeMs),
     pressure: pressure(binding, now, config, view.turnsLeft),
   });

package/skills/usage-limits/scripts/usage.js

@@ -772,6 +772,9 @@ function collect(now) {
 // was spent inside the window it describes equalled its percentage. That
 // dollars-per-point figure is a property of the plan, not of the moment, so it
 // still prices the window running now.
+// Anything above this and the calibration, not the budget, is what is full.
+const SATURATION_LIMIT = 105;
+
 function reconstructWindow(spec, snapshot, events, now) {
   if (!snapshot || typeof snapshot.utilization !== 'number') return null;
   if (snapshot.utilization <= 0) return null;
@@ -786,9 +789,18 @@ function reconstructWindow(spec, snapshot, events, now) {
   const usdPerPercent = past.cost / snapshot.utilization;
   const liveStart = now - spec.span;
   const live = totals(events.filter((e) => e.at >= liveStart && e.at <= now));
+  const raw = live.cost / usdPerPercent;
+
+  // A rebuild that overflows the window is not a full window, it is a broken
+  // calibration. Local transcripts only see this machine, so if the closed
+  // window was mostly spent elsewhere its price per point comes out far too
+  // small and any live spend divides to hundreds of percent. Capping that at
+  // 100 would report a full budget to someone sitting at half, which is worse
+  // than admitting the reading cannot be rebuilt.
+  if (raw > SATURATION_LIMIT) return null;
 
   return {
-    percentUsed: Math.min(100, Math.round(live.cost / usdPerPercent)),
+    percentUsed: Math.min(100, Math.round(raw)),
     usdPerPercent,
     spentUSD: live.cost,
     turns: live.turns,
@@ -1236,6 +1248,7 @@ module.exports = {
   readEvents,
   buildWindow,
   reconstructWindow,
+  SATURATION_LIMIT,
   buildWindows,
   bindingWindow,
   dominantEffort,