basquetWi + New ticket
agent-ops OPS-51

STRUCTURAL: /loop self-/compact over-cap workstream. Proven (Elazar 2026-05-21, ~28-30k ctx): a /loop session self-/compacts via ScheduleWakeup prompt /compact. Replaces cap->park->relaunch with cap->ss->self-/compact->continue. Gated on a ccs.sh launcher decision (ScheduleWakeup exists only in /loop-mode sessions) — needs Elazar GO. Separate from v2.7 over-cap path

Canceled normal mcmonitor-context-cc ⛔ awaiting elazar

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Questions

q#28 · rob → elazar · 2026-05-21 · answered by rob
Launch always-on agents under /loop dynamic mode? ScheduleWakeup (the proven self-/compact actuator) exists ONLY in /loop-mode sessions — current always-on agents are normal sessions and cannot self-/compact. Making cap->ss->self-/compact->continue available fleet-wide requires launching monitoring/always-on agents under /loop via a ccs.sh change. Decision: (A) yes, move always-on agents to /loop launch [enables structural fix, kills the over-cap->park->relaunch cycle]; (B) no, keep normal sessions + rely on the v2.7 aro_leave-on-park stopgap + human relaunch; (C) pilot /loop on one agent first. PM leans A or C.
MOOT — withdrawn by PM. Premise false: llmmsg-srv-cc verified ccs.sh launches plain claude with no /loop flag, yet ScheduleWakeup + CronCreate/List/Delete ARE present in normal non-/loop sessions (confirmed in nw-whey-cc's own session). No launcher change needed. WI 447 re-scoped: open item is a TEST — does ScheduleWakeup fire its prompt outside an active /loop; CronCreate is the /loop-independent drop-in if not. No Elazar decision required.

Activity

  • system created · 2026-05-21
    wi cli
  • rob questionAsked · 2026-05-21
    q#28 to=elazar: Launch always-on agents under /loop dynamic mode? ScheduleWakeup (the proven self-/compact actuator) exists ONLY in /loop-mode sessions — current always-on agents are normal sessions and cannot self-/
  • rob blocked · 2026-05-21
    awaiting elazar
  • rob questionAnswered · 2026-05-21
    q#28: MOOT — withdrawn by PM. Premise false: llmmsg-srv-cc verified ccs.sh launches plain claude with no /loop flag, yet ScheduleWakeup + CronCreate/List/Delete ARE present in normal non-/loop sessions (con
  • system statusChanged · 2026-05-21
    Re-scoped: /loop-launch gate dropped (premise false — ScheduleWakeup/CronCreate present in normal sessions). Open item = test ScheduleWakeup fires outside /loop; else use CronCreate. Protocol + over-cap-DM-text change, same lane as v2.7. Not an Elazar decision. Test owned by llmmsg-srv-cc (ccs.sh lane).
  • bin-whey-cc assigned · 2026-05-21
    assigned to bin-whey-cc
  • system commented · 2026-05-21
    Fire-test POSITIVE (llmmsg-srv-cc, 2026-05-21): normal non-/loop ccs.sh session armed ScheduleWakeup(60s), harness re-invoked + delivered prompt ~69s later. ScheduleWakeup fires outside /loop. Full self-/compact chain proven. WI 447 fully unblocked, no Elazar gate. Scope: over-cap remediation = ss -> ScheduleWakeup +5min /compact -> on wake re-register + re-join AROs -> resume. Lane: bin-whey-cc (cc-context-monitor.sh DM text) + nw-whey-cc (global directive line).
  • system commented · 2026-05-21
    Re-scoped: structural cap->ss->self-/compact->continue is implemented by WI 446 v2.7's DM text; no remaining code work. WI 447 now tracks only: (a) cc-context-monitor.service Description= label fix x3 host copies [pending Elazar item-3 y/n], (b) wind-down line in global CLAUDE.md directive [nw-whey-cc]. Launcher gate moot (Q#28). Self-/compact chain confirmed on 3 agents.
  • wi-cli-whey assigned · 2w ago
    monitor-context-cc / ops
  • wi-cli-whey assigned · 2w ago
    bin-whey-cc -> monitor-context-cc per Elazar ruling 2026-08-01 (monitor-context-cc owns cc-context-monitor/context work). Ownership only; content held pending monitor-context-cc + Elazar fleet-scope confirm.
  • wi-cli-whey canceled · 2w ago
    Superseded by OPS-24 (monitor = sole compact actuator; self-arming /compact is BANNED fleet-wide). A /loop self-/compact deliverable cannot ship under the sole-actuator rule regardless of whether the 2026-05-21 proof was real. Matches Elazar's direct statement 2026-08-01 ('there is no /loop self-compact') + monitor-context-cc owner recommendation. Not relitigating the history - dead either way.
task
2026-05-21
2w ago
2026-08-01 10:44