Bug Description
Bug Report: /loop slash command not recognized in v2.1.71
Version: 2.1.71 (Claude Code)
Platform: macOS (Darwin 25.4.0, arm64)
Installation: Standalone binary (~/.local/share/claude/versions/2.1.71)
Problem
The /loop slash command, introduced in the https://code.claude.com/docs/en/changelog, is not recognized. Typing /loop returns:
Unknown skill: loop
Steps to Reproduce
- Install or update to Claude Code v2.1.71
- Start an interactive session: claude
- Type /loop 1m say hello
- Observe: "Unknown skill: loop"
Expected Behavior
Per the changelog: "/loop command runs a prompt or slash command on a recurring interval (e.g. /loop 5m check the deploy)"
Workaround
The underlying CronCreate tool works correctly and achieves the same functionality:
- CronCreate with cron expression */5 * * * * and a prompt successfully schedules recurring jobs
- CronList and CronDelete also work as expected
- Jobs fire when REPL is idle, auto-expire after 3 days
Analysis
The cron scheduling infrastructure is fully functional — only the /loop slash command surface is broken. Likely either:
- /loop is behind a feature flag not yet enabled for all users
- The slash command registration is missing despite the underlying tools being available
- A rollout issue where the changelog shipped ahead of the feature
Environment Info
- Platform: darwin
- Terminal: Apple_Terminal
- Version: 2.1.71
- Feedback ID: 2d608ae8-73a5-48c2-a784-c06e9d21d99a
Errors
[{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18189)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:06.822Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at A (/$bunfs/root/src/entrypoints/cli.js:106:220)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:106:434)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18260)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:06.823Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18189)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:07.095Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at A (/$bunfs/root/src/entrypoints/cli.js:106:220)\n at <anonymous> (/$bunfs/root…
Note: Content was truncated.
Bug Description
Bug Report: /loop slash command not recognized in v2.1.71
Version: 2.1.71 (Claude Code)
Platform: macOS (Darwin 25.4.0, arm64)
Installation: Standalone binary (~/.local/share/claude/versions/2.1.71)
Problem
The /loop slash command, introduced in the https://code.claude.com/docs/en/changelog, is not recognized. Typing /loop returns:
Unknown skill: loop
Steps to Reproduce
Expected Behavior
Per the changelog: "/loop command runs a prompt or slash command on a recurring interval (e.g. /loop 5m check the deploy)"
Workaround
The underlying CronCreate tool works correctly and achieves the same functionality:
Analysis
The cron scheduling infrastructure is fully functional — only the /loop slash command surface is broken. Likely either:
Environment Info
Errors
[{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18189)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:06.822Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at A (/$bunfs/root/src/entrypoints/cli.js:106:220)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:106:434)\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18260)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:06.823Z"},{"error":"Error: ripgrep exited with code null\n at <anonymous> (/$bunfs/root/src/entrypoints/cli.js:104:18189)\n at emit (node:events:98:22)\n at #maybeClose (node:child_process:766:16)\n at #handleOnExit (node:child_process:520:72)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-03-07T07:20:07.095Z"},{"error":"RipgrepTimeoutError: Ripgrep search timed out after 20 seconds. The search may have matched files but did not complete in time. Try searching a more specific path or pattern.\n at A (/$bunfs/root/src/entrypoints/cli.js:106:220)\n at <anonymous> (/$bunfs/root…Note: Content was truncated.