Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Bug] /remote command not implemented or account not enabled (Max20) [1 comments, 2 participants]

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…
GitHub stats
anthropics/claude-code#53374•Fetched 2026-04-26 05:17:25
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
0
Author
sammcjsammcj
Participants
github-actions[bot]github-actions[bot]sammcjsammcj
Timeline (top)
labeled ×5commented ×1subscribed ×1

Error Message

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/samm/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T22:18:21.578Z"}]

Code Example

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/samm/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n    at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n    at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T22:18:21.578Z"}]

---

▸ unset DISABLE_TELEMETRY CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
▸ grep -iE 'telemetry|nonessential' ~/.claude/settings.json*
▸ claude remote-control
Error: Remote Control is not yet enabled for your account.

---

! env|grep -iE 'telemetry|nonessential'
❯ /remote
❯ Unknown command: /remote

---

▸ claude auth status
{
  "loggedIn": true,
  "authMethod": "claude.ai",
  "apiProvider": "firstParty",
  "email": "redacted",
  "orgId": "redacted",
  "orgName": "redacted's Organization",
  "subscriptionType": "max"
}
RAW_BUFFERClick to expand / collapse

Bug Description

  • /remote does not work: Unknown command: /remote
  • $ claude remote-control results in Error: Remote Control is not yet enabled for your account.

Tried:

  • Always running the latest version (native installer)
  • Ensuring telemetry is enabled (one would hope that this should not be a requirement)
  • Logging out, in
  • Different machines

Env:

  • No proxy, AI gateway or custom endpoint
  • No managed settings
  • No CLAUDE_CODE_OAUTH_TOKEN or any other custom auth token used

Similar to #29513 #28816 #29164 #28278 (all which has been closed without a fix)

Environment Info

  • Platform: darwin
  • Terminal: ghostty
  • Version: 2.1.119
  • Feedback ID: 8c385999-f1f6-4d3a-8369-3446515cc385

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/samm/.local/share/claude/versions/2.1.119 (expected in multi-process scenarios)\n    at mH6 (/$bunfs/root/src/entrypoints/cli.js:2736:2177)\n    at E$8 (/$bunfs/root/src/entrypoints/cli.js:2736:1257)\n    at processTicksAndRejections (native:7:39)","timestamp":"2026-04-25T22:18:21.578Z"}]
▸ unset DISABLE_TELEMETRY CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
▸ grep -iE 'telemetry|nonessential' ~/.claude/settings.json*
▸ claude remote-control
Error: Remote Control is not yet enabled for your account.
! env|grep -iE 'telemetry|nonessential'
❯ /remote
❯ Unknown command: /remote
▸ claude auth status
{
  "loggedIn": true,
  "authMethod": "claude.ai",
  "apiProvider": "firstParty",
  "email": "redacted",
  "orgId": "redacted",
  "orgName": "redacted's Organization",
  "subscriptionType": "max"
}

extent analysis

TL;DR

The issue with /remote not working and Remote Control is not yet enabled for your account error may be related to account settings or telemetry requirements.

Guidance

  • Verify that Remote Control is enabled for the account by checking the account settings or contacting support.
  • Check if there are any specific requirements or restrictions for using Remote Control with the current subscription type (max).
  • Review the error message Error: Remote Control is not yet enabled for your account and the output of claude auth status to ensure that the account is properly configured.
  • Consider checking the official documentation or support channels for any known issues or limitations related to Remote Control.

Notes

The issue seems to be related to account settings or telemetry requirements, but the exact cause is unclear. The provided error messages and output do not indicate a clear technical issue with the installation or configuration.

Recommendation

Apply workaround: Contact support to verify Remote Control settings and requirements for the account, as the error message suggests that it may not be enabled.

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#API rate limit#retriever error#indexing error#inference speed

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 [Bug] /remote command not implemented or account not enabled (Max20) [1 comments, 2 participants]