[BUG] Slash commands `/remote-control`, `/rc`, `/btw` not available for Team plan `primary_owner` - CLI `claude remote-control` works

Status Fixed / completed
Reported on v2.1.72
Maintainer reply None cached
Activity 7 comments · opened Mar 11, 2026 · closed Mar 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

On a Team plan, the primary_owner of the organization does not see plan-gated slash commands (/remote-control, /rc, /btw) inside an active session, while other team members on the same subscription do.

The CLI command claude remote-control works correctly — only the in-session slash commands are missing.

After a full reinstall (native → Homebrew) and fresh login (deleted ~/.claude.json, re-authenticated via OAuth), the hasAvailableSubscription field is never written to ~/.claude.json. Team members with organizationRole: "member" reportedly have this field set to true.

What Should Happen?

  • /remote-control, /rc, and /btw should be available as slash commands inside an active session
  • hasAvailableSubscription should be set to true after OAuth login for a primary_owner on a Team plan
  • The primary_owner should have at least the same feature access as regular team members

Error Messages/Logs

Steps to Reproduce

  1. Be the primary_owner of a Team plan organization
  2. Install Claude Code via Homebrew (brew install --cask claude-code)
  3. Run claude and authenticate via /login (OAuth through claude.ai)
  4. Open a session and type / to see available commands
  5. /remote-control, /rc, and /btw are missing from the list
  6. Exit and run claude remote-control from the terminal — this works correctly
  7. Inspect ~/.claude.jsonhasAvailableSubscription is absent

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.72

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

Relevant ~/.claude.json fields

{
  "oauthAccount": {
    "emailAddress": "",
    "organizationRole": "primary_owner",
    "billingType": "stripe_subscription",
    "hasExtraUsageEnabled": false
  },
  "cachedExtraUsageDisabledReason": "org_level_disabled",
  "penguinModeOrgEnabled": false
}

Note: hasAvailableSubscription is completely absent — not false, just missing. Other team members (organizationRole: "member") on the same org reportedly have hasAvailableSubscription: true.

Environment

  • Claude Code version: 2.1.72
  • Install method: Homebrew (previously native — fully cleaned up, no leftover files in ~/.local/)
  • OS: macOS
  • Auth method: OAuth (claude.ai)
  • Plan: Team (stripe_subscription)
  • Organization role: primary_owner

Additional Context

  • A full reinstall cycle was performed: uninstalled native, removed ~/.local/share/claude and ~/.local/bin/claude, installed via Homebrew, deleted ~/.claude.json, re-authenticated — issue persists
  • The CLI command claude remote-control works, suggesting the server-side entitlement is correct but the client-side slash command visibility check is failing
  • Possibly related to #28322, #33119, and #28773, but distinct because those don't identify the primary_owner role as the root cause

View original on GitHub ↗

7 Comments

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/33119
  2. https://github.com/anthropics/claude-code/issues/30756
  3. https://github.com/anthropics/claude-code/issues/31606

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

Caylub · 5 months ago

I'm not on a Team/Enterprise plan (I've got a 20x Max subscription), and I'm seeing the same things. Basically none of the features of the last many updates are available to me. Whatever feature gating you guys are doing is broken for a bunch of users. I would suspect there are not more people complaining about these issues, because they are simply not aware that these features exist. But I see several others with these features (mix bag of Team/Enterprise and Max plans) without any issues.

See also: https://github.com/anthropics/claude-code/issues/33119

cc @bcherny @ant-kurt

tksohishi · 5 months ago

Same issue here. Max 5x plan, macOS (Darwin 25.3.0), Claude Code v2.1.74.

  • claude remote-control from the CLI works fine
  • /remote-control, /rc, and /btw don't appear in slash command autocomplete
  • Tried full /logout + /login cycle and reinstalling the binary, no change
Caylub · 5 months ago

One common cause for missing /remote-control, /rc, /btw on personal Max plans: CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC=1 or DISABLE_TELEMETRY set in your shell environment. This silently disables all GrowthBook feature flag evaluation — XA() returns the default false for every flag without checking cached values. Commands simply don't appear with no error.

Fix: remove the env var from your shell profile and restart your shell.

Full root cause analysis: https://github.com/anthropics/claude-code/issues/33119#issuecomment-4052694908

Note: This won't fix the Team plan primary_owner issue described in the OP, which appears to be a separate server-side entitlement problem.

tksohishi · 5 months ago

Removing CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC and DISABLE_TELEMETRY from my settings fixed it. /rc and /btw are both showing up now. Thanks @Caylub for the root cause analysis!

yaronya · 5 months ago

I removed DISABLE_TELEMETRY from my ~/.claude/settings.json (honestly have no clue why it was there) and I see all missing features now.
Closing this issue.

github-actions[bot] · 5 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.