[BUG] slash command /btw shown in tips but returns 'Unknown skill' when feature flag isn't enabled.

Additional finding: DISABLE_TELEMETRY env var prevents feature flag resolution

I can confirm this is related to feature flag fetching. In my case, /btw works in some
project directories but not others. After isolating variables:

Root cause: Setting DISABLE_TELEMETRY in .claude/settings.json env config prevents the server-side feature flag from being fetched, so /btw is never enabled.

Reproduction:

// .claude/settings.json — /btw does NOT work
{
  "env": {
    "DISABLE_TELEMETRY": "1"
  }
}

// .claude/settings.json — /btw WORKS
{
  "env": {}
}

Note: setting DISABLE_TELEMETRY to "0" still suppresses /btw - the check appears to be presence-based, not value-based.

Environment: Claude Code v2.1.74, macOS, Anthropic API (Opus 4.6)

Workaround: Remove DISABLE_TELEMETRY from your .claude/settings.json env section.

This is wild and borderline unconscionable, the mechanism for managing feature flags and having to opt in to telemetry should not be linked.

It's not related to DISABLE_TELEMETRY but as soon as any environment variable is set, btw will not work. Seems like there is a broken feature flag check. Removing env from .claude/settings.json fixes the issue for me.

@masta79 I think it is, or at least it's related to some specific env vars, because I have both ENABLE_TOOL_SEARCH and BUTTS (just something random) set and /btw works.

I'll also note that /remote-control hadn't been working for me as an in-session command until I removed DISABLE_TELEMETRY as well, so this ticket actually fixed both of those problems for me. The unfortunate thing is I don't _want_ telemetry enabled, and it clearly doesn't cache those feature flag checks since the commands disappear again if I put the line back. So yeah, very unfortunate coincidence or (IMO more likely) the concerns that phone home are commingled.

@tumes its been this way for some time. basically every new feature that's come out for months doesn't work out of the box unless you remove DISABLE_TELEMETRY. have to imagine its on purpose - can't be a complicated thing to "fix"

+1, please fix this wild bug, thanks

Additional finding: DISABLE_TELEMETRY env var prevents feature flag resolution I can confirm this is related to feature flag fetching. In my case, /btw works in some project directories but not others. After isolating variables: Root cause: Setting DISABLE_TELEMETRY in .claude/settings.json env config prevents the server-side feature flag from being fetched, so /btw is never enabled. Reproduction: `` // .claude/settings.json — /btw does NOT work { "env": { "DISABLE_TELEMETRY": "1" } } ` ` // .claude/settings.json — /btw WORKS { "env": {} } ` Note: setting DISABLE_TELEMETRY to "0" still suppresses /btw - the check appears to be presence-based, not value-based. Environment: Claude Code v2.1.74, macOS, Anthropic API (Opus 4.6) **Workaround:** Remove DISABLE_TELEMETRY from your .claude/settings.json` env section.

i don't have DISABLE_TELEMETRY in my env but a bunch of other env settings, still can't see /btw, i think this is not specifically to DISABLE_TELEMETRY existence

i don't have DISABLE_TELEMETRY in my env but a bunch of other env settings, still can't see /btw, i think this is not specifically to DISABLE_TELEMETRY existence

Check this
I have Claude Code v2.1.77
Remove "CLAUDE_CODE_DISABLE_FEEDBACK_SURVEY": "1" and /btw show up

since 2.1.79, it shows up

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

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.