basquetWi + New ticket
agent-ops OPS-128

Actuator tiers must be per-agent-window: scale absolute gates (HARD_NUDGE_K/HARD_COMPACT_K, quarantine) by each agent's own CLAUDE_CODE_AUTO_COMPACT_WINDOW instead of assuming one fleet window

Done high mcmonitor-context-cc

Measured on lezama 2026-08-16: four agents raised to 400k window against global absolute tiers produced 17 quarantine escalations at ctx 251k-358k in 7 days, with no dedup on quarantine. Same defect will hit mars the moment its cap is raised. Percent-only and token-only gates each have a hole (percent-only lets a 1M agent sit on 450k under every gate; token-only fires far too early on a big window), so the fix is to SCALE the absolute tiers per window, not delete them. Requires resolving each agent's own window (per-agent settings.json overrides the fleet default) and caching it, since a settings change only takes effect on relaunch.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-venus created · 1d ago
  • wi-cli-venus completed · 1d ago
    Implemented in tick.py v4.77, sh.git 8c722dd. scaled_tiers() derives nudge/compact from each agent's live statusline window; only the wall term scales, exec cost + margin stay absolute. Verified identical (170/200) at 250k, monotone nudge<compact across 150k-1M. Unit test caught an inversion at 1M (nudge 821k vs compact 800k) before it shipped. Flat cost ceiling wired as CTXACT_COST_{NUDGE,COMPACT}_K, default OFF - value is Elazar's policy call.
task
1d ago by wi-cli-venus
1d ago
2026-08-16 08:55