`/loop` skill loads in web sessions but its backing tools (`CronCreate` / `ScheduleWakeup`) are not loadable

Summary

The /loop skill is announced as available on web sessions (see "Feature of the week" banner in the chat UI), and the skill itself loads into the session's skill registry. But the tools the skill depends on to actually schedule anything — CronCreate (fixed-interval mode) and ScheduleWakeup (dynamic / self-paced mode) — are not present, not deferred-loadable, and not surfaced in ToolSearch. The skill is effectively a no-op past its parsing step.

Banner (Claude Code web UI, 2026-06-05)

Feature of the week: /loop — run a prompt or slash command on a recurring interval [Try it]

Repro

1. Start a fresh Claude Code web session (entrypoint remote_desktop) after the banner appeared. (My prior session was spawned the previous night, before the banner; this fresh session was spawned today, post-banner. Same result.)
2. Invoke /loop 2m <prompt> (any interval, any prompt).
3. The /loop skill loads from the registry and dispatches per its parsing rules.
4. The skill instructs the agent to "Call CronCreate with: cron (the expression above), prompt (the parsed prompt verbatim), recurring: true."
5. CronCreate is not in the up-front tool list. Searching for it via the deferred-tool registry:

``
ToolSearch query="select:CronCreate,CronDelete,CronList" → "No matching deferred tools found"
ToolSearch query="cron schedule recurring" → returns Monitor + Google Calendar create_event; no CronCreate / ScheduleWakeup
ToolSearch query="ScheduleWakeup send_later wakeup" → "No matching deferred tools found"
``

1. Neither the fixed-interval path (CronCreate) nor the dynamic / self-paced path (ScheduleWakeup) can execute. The loop never schedules.

Expected

If /loop is in the web session's skill registry, the tools it documents calling (CronCreate, optionally ScheduleWakeup) should be either loaded up-front or available via ToolSearch so the skill can drive them.

Actual

/loop is present and dispatchable; its dependencies are absent. The skill's own description explicitly names CronCreate and ScheduleWakeup as required tools.

Environment

• Surface: Claude Code web (claude.ai/code)
• Entrypoint: remote_desktop
• Container OS: Linux 6.18.5
• Model: claude-opus-4-7[1m]
• Date of repro: 2026-06-05

Workaround

None at present from the agent's side — Monitor is process-bound (stdout-line events from a long-running script), not a cron-style scheduler, and doesn't satisfy the skill's contract. A loop can be simulated by re-invoking the prompt manually, which defeats the point of /loop.

Note

I'm not sure whether the gap is (a) the skill having shipped to the web registry before the backing tools, or (b) the backing tools being gated behind a flag that isn't on for this account/session type. Either is fine to confirm in a reply — happy to provide additional environment dumps if useful.

https://claude.ai/code/session_01KBwv8ejhPJbXXVYYFikYzq