Max plan: 1M context window shows 200k, Remote Control unavailable

[stripped-down]

Environment

• Claude Code version: 2.1.75
• Plan: Max (20x, confirmed at claude.ai/settings/billing)
• OS: macOS (Apple Silicon, M3 Max)
• Model: Opus 4.6 (Default)

Issue

Two features that should be available on the Max plan are not working:

1. Context window stuck at 200k instead of 1M

The v2.1.75 changelog states:

Added 1M context window for Opus 4.6 by default for Max, Team, and Enterprise plans (previously required extra usage)

However, /context consistently shows 200k as the context window size, not 1M:

claude-opus-4-6 · 35k/200k tokens (18%)

Verified:

• CLAUDE_CODE_DISABLE_1M_CONTEXT is not set
• Restarted Claude Code (full exit + relaunch) - still 200k
• No managed settings or local config overriding context window
• Running latest version (2.1.75)

2. Remote Control not available

Remote Control has been announced for Max plans but is not accessible on this account.

Expected behaviour

• /context should show Xk/1000k tokens (1M context window)
• Remote Control should be available

Steps to reproduce

1. Subscribe to Max plan (20x)
2. Install Claude Code 2.1.75
3. Run claude and check /context
4. Observe 200k limit instead of 1M

[github-actions]

Found 3 possible duplicate issues:

1. [Bug] /context command reports 200K max for Claude Opus 4.6 instead of 1M #23432
2. Claude Opus 4.6 context display shows 200k instead of 1M #24208
3. Opus/Sonnet 1M context variants broken on Max 20x — misleading 'Rate limit reached' error #30163

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

[lopi-py]

Enable telemetry. I had the same issue with 1M context not showing and /remote-control not working, just enabled telemtry and it's working now. PLEASE ANTHROPIC WHY?? WHAT'S THE REASONING?? I HOPE THIS IS A BUG THIS CAN'T BE HAPPENING

[certiv-dwager]

Enable telemetry. I had the same issue with 1M context not showing and /remote-control not working, just enabled telemtry and it's working now. PLEASE ANTHROPIC WHY?? WHAT'S THE REASONING?? I HOPE THIS IS A BUG THIS CAN'T BE HAPPENING

Yeah, this is it. my guess is they're doing a rollout right now, and they want to watch their metrics closely. so rolling out to telemetry enabled users first.

[inevity]

"CLAUDE_CODE_ENABLE_TELEMETRY": "1",
still 200K

[cwilso03]

"CLAUDE_CODE_ENABLE_TELEMETRY": "1", still 200K

Check your ~/.claude/settings.json file. Look for a section like this:

  "env": {
    "DISABLE_TELEMETRY": "1"
  },

and delete it.

I was having the same issue. I can confirm that removing the above from settings.json and then restarting Claude Code immediately made 1M context available. And, if I added the above back in, I lost the 1M context.

Hopefully the need to enable telemetry is temporary while they roll out the feature to all users.

[stripped-down]

Update: I set up a fresh Linux VM (same account, same Max plan, same version 2.1.76) and it immediately has 1M context and /remote-control. My macOS (Apple Silicon, M3 Max) still shows 200k and no /remote-control.

Telemetry is enabled on both. Tried fresh reinstalls, logout/login, clearing statsig cache - nothing works on macOS. Seems like the rollout is platform-gated (Linux first, macOS not yet).

[Nantris]

It's just random. I use it across several machines with identical settings and some have 1M and some don't. Most don't.

Edit: I don't think you're missing out though. I've been trying to figure out why Claude has been so dumb and useless all day and I'm pretty sure the 1 million context window is the answer. Unless it's a coincidence this seems like worst model Claude model I've ever used.