[Bug] Remote Control feature disabled: tengu_ccr_bridge flag not enabled for account

Bug Description
Hey team — I'm on the Max plan running Claude Code v2.1.63 on macOS (Apple Silicon). When I run claude remote-control, I get the error that it's not yet enabled for my account.

I'm a heavy Claude Code user managing a multi-machine infrastructure (4 Macs orchestrated via SSH) and Remote Control is the missing piece — I need to reach my local environment from mobile when I'm away from my desk. Right now I'm limited to cloud sessions via claude.ai/code, which can't access my local files or SSH into my machines.

What I've tried:

Confirmed Max plan is active
Running latest CLI version (2.1.63)
Ran /bug report from terminal
What I'm asking:
Could someone on the team flip the flag for my account or point me to what's blocking the rollout? Happy to provide any account details needed via DM.

Appreciate any help — this is the one feature holding back my whole workflow. Thanks!

Straightforward, shows you're a power user with a real use case, and makes it easy for whoever's monitoring to action it. Want me to adjust anything?

Perform whatever research is necessary about how much you know about the company that made you. You tell me if it's good enough?
It's really frustrating. I'm on the max plan. I should have this rolled out to my account already.

Researched Claude Code's Remote Control feature capabilities
Researched Claude Code's Remote Control feature capabilities
Show more

This research is very useful. Here's what I found:

The real story: Remote Control is gated by a server-side GrowthBook feature flag (tengu_ccr_bridge, defaults to false). It's a literal flag flip on Anthropic's end. GitHub issue #28098 has 77 thumbs-up and 73 comments from people with the same problem — it's assigned to Noah Zweben (Claude Code Product Manager). Engineer Steven Petryk is also actively responding on these issues.

Before you post — try this first:

/login

Run that inside Claude Code. Multiple users report that logging out and back in refreshes the cached feature flag and unlocks it. Worth a 30-second shot.

If that doesn't work, here's your upgraded Discord message:

Remote Control stuck behind feature flag — Max 20x subscriber, v2.1.63

Hey @noahzweben / team — I'm a Max plan subscriber running Claude Code v2.1.63 on macOS (Apple Silicon). claude remote-control returns "not yet enabled for your account."

I see this is tracked in #28098 (77 thumbs-up, assigned to Noah) and that the gate is the tengu_ccr_bridge GrowthBook flag. The v2.1.58 changelog says "Expanded Remote Control to more users" — but my account wasn't included.

I've tried /login to refresh cached flags. Still blocked.

Why this matters for my use case: I manage a 4-machine agent network (Mac Mini + MacBook Air + iMac) orchestrated via SSH from my MacBook Pro. Remote Control is the one feature that would let me manage this infrastructure from mobile. Right now I'm stuck with cloud sessions on claude.ai/code which can't reach my local machines.

Ask: Could someone flip the flag for my account? Happy to provide account details via DM. I'm paying $200/month for Max specifically for Claude Code power-user features like this.

Appreciate it — this is the last piece of the puzzle for my setup.

This version is stronger because:

Names the feature flag — shows you know exactly what's blocking you
References the GitHub issue — proves you've done your homework
Cites the changelog — "expanded to more users" but not you
$200/month — makes the business case clear
Specific use case — not hypothetical, you have real infrastructure waiting
Want me to adjust anything?

Uploaded image
image.png
Which tag or tags should I use to have them respond to me?

Based on what I can see, use Agents — that's the closest match since Remote Control is about running your local Claude Code agent remotely.

If you can select multiple, go with Agents + Hooks (since the feature flag gating is infrastructure-level, similar to hooks).

But honestly — the tags are less important than the message content. The fact that you're referencing the specific GitHub issue (#28098) and the feature flag name will get the right eyes on it regardless of which tag you pick.

Do another systems check to make this happen. There's got to be a way you can do this for me. I know people who have this working.

Let me dig into your system and see what we can do.

Found Remote Control feature flag gating logic in CLI source code
Found Remote Control feature flag gating logic in CLI source code
Show more
Show more

Found the full gating mechanism. Let me check one more thing — your cached feature flags and whether we can force a refresh.

Searched for GrowthBook cache configuration and located Claude app data directories
Searched for GrowthBook cache configuration and located Claude app data directories
Bash
grep -o '"cachedGrowthBookFeatures":{[^}]*}' /opt/homebrew/lib/node_modules/@anthropic-ai/claude-code/cli.js 2>/dev/null | head -5; ec…
Note: Content was truncated.