/loop Explicit Stop via ScheduleWakeup({stop: true}) / Claude Code v2.1.202

What

The ScheduleWakeup tool used in dynamic /loop sessions now accepts a stop: true field to explicitly terminate the loop, replacing the previous implicit approach of simply omitting the call.

Details

stop: true cancels all pending wakeups and records a terminal event
When called after the loop has already ended, it logs a cleanup-only message and suppresses the terminal event to avoid double-firing
The /loop instructions now clearly enumerate step 6: "To stop the loop — call ScheduleWakeup with stop: true (no other fields) ... Stopping is the loop's normal ending — the user can restart it anytime with /loop."
A loopEnded flag is now tracked in session state to guard against duplicate stop events
A noop field was already present; delaySeconds, reason, and prompt are now explicitly documented as required only when stop is not true
The tool description now reads: "call with stop: true to end the loop immediately" (was: "omit the call to end it")

Evidence

Loop stop handler (search for "[loop] model called ScheduleWakeup({stop:true})" and "stop the /loop — cancel pending wakeups, schedule nothing")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.