▣ wi

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

Ref

#447 (#447)

Project

agent-ops

Status

todo

Priority

normal

Type

task

Assigned

bin-whey-cc coder

Created by

—

Blocked reason

awaiting elazar

Created

2026-05-21T06:23:50.291Z

Updated

2026-05-21T07:12:24.744Z

Sub-items

Questions

• 2026-05-21T06:24:17.002Z · q#28 · asked by rob → elazar · answered 2026-05-21T06:25:50.364Z 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.
  answer: 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.

Event log

• 2026-05-21T06:23:50.292Z · created
  wi cli
• 2026-05-21T06:24:17.003Z · questionAsked · rob
  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-/
• 2026-05-21T06:24:17.004Z · blocked · rob
  awaiting elazar
• 2026-05-21T06:25:50.364Z · questionAnswered · rob
  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
• 2026-05-21T06:25:50.422Z · statusChanged
  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).
• 2026-05-21T06:28:39.153Z · assigned · bin-whey-cc
  assigned to bin-whey-cc
• 2026-05-21T06:28:39.189Z · commented
  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).
• 2026-05-21T07:12:24.744Z · commented
  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.