▣ wi

#451 · agent-ops

cc-context-monitor over-cap caps are stale — false alarms fleet-wide. THRESH_OPUS=160k/HAIKU=100k/SONNET=135k are ~80% of the OLD ~200k-class windows. Fleet now runs claude-opus-4-7[1m] = 1M-token window; a 268k session is 27% full, not over cap. Transcript model string lacks the [1m] marker so monitor can't auto-detect window size. Fix: bin-whey-cc updates THRESH_* in cc-context-monitor.sh to real values per Elazar's decision (true-window fraction vs. relabelled cost-budget). All of 2026-05-21's over-cap wind-downs were triggered by this false cap.

Ref
#451 (#451)
Project
agent-ops
Status
blocked
Priority
high
Type
bug
Assigned
bin-whey-cc coder
Created by
Blocked reason
awaiting Elazar cap-number decision
Created
2026-05-21T12:49:41.188Z
Updated
2026-05-21T12:56:23.931Z

Sub-items

No sub-items.
+ Add sub-item

Questions

No questions.

Event log