Skip to content

Session D brief — Vendor usage-reset feed watcher (FLT-26)

Branch wt/WT-0026/FLT-26-usage-reset-feed off master 3bee437. Worktree isolation. usage-governor repo.

Problem (user-directed 2026-07-17)

Vendors (Anthropic, OpenAI/Codex, xAI/Grok, Google/Antigravity) sometimes RESET usage limits MID-WEEK, out of band. Proven this week — a reset gave unexpected bandwidth. The governor only knows its own local burn ledger, so it stays conservative (RED) when we actually have headroom, throttling the fleet for no reason.

Build

A feed/RSS/status watcher (C#, fits UsageGovernor.Core) that polls each vendor's official signal for reset events and updates governor state so tiers reflect reality. - Sources (prefer an authoritative usage/quota API where one exists; status-page/RSS is fallback): - Anthropic — status.anthropic.com + any Claude usage signal - OpenAI/Codex — status.openai.com + ChatGPT usage - xAI/Grok — xAI status - Google/Antigravity — status - On a DETECTED reset, ratchet the governor budget back UP. This is the inverse of scan-usage.ps1 -RecordLimitHit (which ratchets DOWN 20% on a real limit hit). Find and mirror that path. - Integrate with the governor state the hooks read (state.json / the tier the PreToolUse gate uses).

Hard rules

  • NEVER auto-loosen on an unverified signal. Fail toward conservative. A false "reset" that loosens the gate = overspend. Require a clear, authoritative reset indicator, not a fuzzy status-page word.
  • Council the design FIRST (this is a spend-control change): polling cadence, how to distinguish a real reset from noise/flapping, what counts as authoritative per vendor, and the fail-conservative default.
  • Separate from the CLI balancer (#18) and the fleet-global admit ledger (#17, LANDED — admit authority runs on DESKTOP-D249KD4:47610, see [[cli-balancer-council-verdict]]).

Context

  • Governor tiers: GREEN/YELLOW/RED/BLACKOUT. RED is often PROJECTION-driven (projectedPct high while actual pctUsed low) — a reset watcher helps correct false-RED.
  • scan-usage.ps1, AgyPolicy.cs, AgyConfig.cs, GovernorConfig are the relevant surfaces.

Guardrails

C#-first. /council-code-review before commit+push. Verify by artifact (a simulated reset event actually moves the governor tier). Do NOT touch the live admit authority.