[Bug] /loop slash command not recognized in v2.1.71

Resolved 💬 21 comments Opened Mar 7, 2026 by byosamah Closed Apr 19, 2026

💡 Likely answer: A maintainer (bcherny, collaborator) responded on this thread — see the highlighted reply below.

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.

View original on GitHub ↗

21 Comments

boozedog · 4 months ago

I'm seeing same issue on macOS with v2.1.71 ... but my Claude Code does not have the underlying CronCreate tool in its toolset.

❯ Unknown skill: loop

❯ Use the CronCreate tool to schedule a recurring task:
- Cron expression: */5 * * * *
- Prompt: tell me the current time and say hello
- Make it recurring

⏺ It looks like you tried a /loop skill that doesn't exist, and there's a mention of a CronCreate tool which isn't available in my toolset.

eguitarz · 4 months ago

I accidentally fixed it by

brew install sox

I had same issue /loop not found. so I decided to try /voice first.
And it mentions I need to install sox
so I did brew install sox
then, i can see /loop in command line.

boozedog · 4 months ago

❯ Unknown skill: loop

❯ Unknown skill: voice

🤷‍♂️

impxd · 4 months ago

❯ Unknown skill: loop

arjantop-cai · 4 months ago

I accidentally fixed it by > brew install sox I had same issue /loop not found. so I decided to try /voice first. And it mentions I need to install sox so I did brew install sox then, i can see /loop in command line.

This also solved it for me, but I do not have access to /voice yet

boozedog · 4 months ago

installing sox did not change anything for me

i still see brew install sox

i do have CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC enabled i wonder if that might be it

nemoo · 4 months ago

unknown skill: loop

maOS 26.3.1
claude code v2.1.71
Installation: Standalone binary

xiangjianmeng · 4 months ago

let claude code get the two env var unset:
"DISABLE_TELEMETRY": "1",
"CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",

LQY-920 · 4 months ago

Unknown skill: loop

ChenReuven · 4 months ago

same issue (brew install sox dosnt help for me)

droath · 4 months ago

Once I completely removed the "env" from the ~/.claude/settings.json both /loop and /remote-control appeared, but the voice feature did not.

"DISABLE_TELEMETRY": "1"

gburiola · 4 months ago

Seems like /loop is a server side feature flag. Maybe it's not available (yet) if you connect to claude via GCP Vertex?

pranayjswl007 · 4 months ago

Same not available for claude code via bedrock

bcherny collaborator · 4 months ago

Thanks for the detailed reports — confirmed the bug.

Root cause: /loop (and the Cron tools) are gated by a GrowthBook feature flag that defaults to false for external users. GrowthBook is disabled when:

Using Bedrock / Vertex / Foundry
DISABLE_TELEMETRY=1 or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 are set
On first run before the disk cache is populated

When GrowthBook is disabled it returns the default (false externally), so /loop gets filtered out of the slash command list at startup. The Cron tools could still appear for some users because tools re-check their gate on every query (after GrowthBook eventually loads), while slash commands are memoized once at startup.

The brew install sox "fix" was a red herring — it just caused a restart after the GrowthBook disk cache had been populated during the previous session.

Fix: https://github.com/anthropics/claude-cli-internal/pull/21506 — flips the GrowthBook default to true since the feature is GA. The gate now serves purely as a fleet-wide kill switch. Should land in the next release.

gavriil-deshaw · 4 months ago

@bcherny the phrasing

GrowthBook feature flag that defaults to false for external users.

and then:

GrowthBook is disabled when: Using Bedrock / Vertex / Foundry DISABLE_TELEMETRY=1 or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 are set On first run before the disk cache is populated

is confusing. Are the "external users" defined as the ones who satisfy any of those 3 points or are these two separate things?

In other words, when the fix you mention is out, will users that satisfy any of those 3 points still be blocked or will they be able to use /loop?

Quentin-M · 4 months ago

Amazing - just got the feature 👍 🙏
While /simplify landed too, /batch is also missing unfortunately!

boozedog · 4 months ago

/loop is working for me now (although /btw hasn't appeared yet)

dansecops · 4 months ago

Same here, /btw command returns "no response received", occured when claude is implementing a plan
Info:

Claude Code - 2.1.73
MacOS 15.4.1
Installation: Standalone binary from brew

boozedog · 4 months ago

Thanks for the detailed reports — confirmed the bug. Root cause: /loop (and the Cron tools) are gated by a GrowthBook feature flag that defaults to false for external users. GrowthBook is disabled when: Using Bedrock / Vertex / Foundry DISABLE_TELEMETRY=1 or CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 are set * On first run before the disk cache is populated When GrowthBook is disabled it returns the default (false externally), so /loop gets filtered out of the slash command list at startup. The Cron _tools_ could still appear for some users because tools re-check their gate on every query (after GrowthBook eventually loads), while slash commands are memoized once at startup. The brew install sox "fix" was a red herring — it just caused a restart after the GrowthBook disk cache had been populated during the previous session. Fix: https://github.com/anthropics/claude-cli-internal/pull/21506 — flips the GrowthBook default to true since the feature is GA. The gate now serves purely as a fleet-wide kill switch. Should land in the next release.

@bcherny are other GA features possibly still gated (e.g., /btw)? seeing a similar problem here https://github.com/anthropics/claude-code/issues/33129#issuecomment-4081343085

claude[bot] contributor · 2 months ago

This issue was fixed as of version 2.1.72.

github-actions[bot] · 2 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.