Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix /remote-control hidden in Claude Desktop 2.1.111 — injected CLAUDE_CODE_OAUTH_TOKEN is inference-only

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

After updating Claude Desktop to 2.1.111 on Windows, the /remote-control slash command returns /remote-control isn't available in this environment. in the Desktop chat UI. Before the update (same day), the command worked and I used it regularly for mobile access from the Desktop app.

Root Cause

After updating Claude Desktop to 2.1.111 on Windows, the /remote-control slash command returns /remote-control isn't available in this environment. in the Desktop chat UI. Before the update (same day), the command worked and I used it regularly for mobile access from the Desktop app.

Code Example

function vu(){ return Si6() && C8("tengu_ccr_bridge", !1) }
function Si6(){ try{ return s$() } catch{ return !1 } }
RAW_BUFFERClick to expand / collapse

Dear Anthropic team,

Summary

After updating Claude Desktop to 2.1.111 on Windows, the /remote-control slash command returns /remote-control isn't available in this environment. in the Desktop chat UI. Before the update (same day), the command worked and I used it regularly for mobile access from the Desktop app.

Environment

  • OS: Windows 10/11
  • Claude Desktop with Claude Code 2.1.111
  • CLAUDE_CODE_ENTRYPOINT=claude-desktop
  • Subscription: full claude.ai login (not API key); ANTHROPIC_API_KEY unset
  • No third-party provider env vars (CLAUDE_CODE_USE_BEDROCK/_USE_VERTEX/_USE_FOUNDRY all unset)

Reproduction

  1. Update Claude Desktop such that it ships Claude Code 2.1.111
  2. Open any Desktop session
  3. Type /remote-control
  4. Response: /remote-control isn't available in this environment.

Diagnosis (from the shipped claude.exe)

The slash command's enable check:

function vu(){ return Si6() && C8("tengu_ccr_bridge", !1) }
function Si6(){ try{ return s$() } catch{ return !1 } }

The feature flag passes (CLAUDE_INTERNAL_FC_OVERRIDES={"tengu_ccr_bridge":true} is present in the session env), so Si6() must be returning false — which sets isHidden on the slash command and produces the generic stub.

getBridgeDisabledReason (yi6) names the failure mode explicitly:

Remote Control requires a full-scope login token. Long-lived tokens (from claude setup-token or CLAUDE_CODE_OAUTH_TOKEN) are limited to inference-only for security reasons. Run claude auth login to use Remote Control.

Desktop 2.1.111 injects CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-… into every spawned session. That token is inference-only, Si6() returns false, /remote-control is hidden.

Expected

Pre-2.1.111 Desktop built this session with a full-scope token (or no CLAUDE_CODE_OAUTH_TOKEN at all, letting the session resolve auth from the cached oauth:tokenCache in %APPDATA%\Claude\config.json), so /remote-control was available in the Desktop chat UI. Post-update, it is not.

Either:

  • Desktop should not inject an inference-only CLAUDE_CODE_OAUTH_TOKEN when a full-scope claude.ai login is cached in %APPDATA%\Claude\config.json, or
  • The Desktop chat UI should prefer the cached full-scope token for Remote Control eligibility

Thanks!

extent analysis

TL;DR

The most likely fix is to modify the Desktop application to prefer the cached full-scope token for Remote Control eligibility or to not inject an inference-only CLAUDE_CODE_OAUTH_TOKEN when a full-scope claude.ai login is cached.

Guidance

  • Verify that the CLAUDE_CODE_OAUTH_TOKEN injected by Desktop 2.1.111 is indeed inference-only and limited to inference-only for security reasons.
  • Check the config.json file in %APPDATA%\Claude\ to confirm that a full-scope claude.ai login is cached.
  • Consider modifying the claude.exe to check for a cached full-scope token before injecting the CLAUDE_CODE_OAUTH_TOKEN.
  • Investigate the possibility of running claude auth login to obtain a full-scope login token, as suggested by the getBridgeDisabledReason function.

Example

No code snippet is provided as the issue does not require a specific code change, but rather a modification to the application's behavior.

Notes

The issue seems to be related to the change in behavior of the Desktop application after updating to version 2.1.111, specifically with regards to the injection of the CLAUDE_CODE_OAUTH_TOKEN. The exact solution may depend on the internal implementation of the application and the requirements of the Remote Control feature.

Recommendation

Apply a workaround by running claude auth login to obtain a full-scope login token, as this is the suggested solution by the getBridgeDisabledReason function. This may provide a temporary fix until the underlying issue is resolved.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#request timeout

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix /remote-control hidden in Claude Desktop 2.1.111 — injected CLAUDE_CODE_OAUTH_TOKEN is inference-only