remote-control silently fails when DISABLE_TELEMETRY is set to 0 or 1
Resolved 💬 4 comments Opened Mar 28, 2026 by bonanza465 Closed Apr 1, 2026
Bug
/remote-control (and claude --remote-control) silently fails to activate when DISABLE_TELEMETRY is set in settings.json. No error message is shown — the command simply does nothing.
Steps to Reproduce
- Add
"DISABLE_TELEMETRY": "1"toenvin~/.claude/settings.json - Restart Claude Code
- Run
/remote-controlor/rc
Expected: Error message explaining that Remote Control requires telemetry to be enabled
Actual: "Unknown skill: remote-control" — the slash command doesn't register at all
Additional Context
- Claude Code version: 2.1.84
- Platform: WSL2 (Linux 6.6.87.2-microsoft-standard-WSL2)
- Setting
DISABLE_TELEMETRYto"0"still breaks it (non-empty string is truthy) — the key must be removed entirely or set to "" - Debug logs confirm:
isTelemetryEnabled=false (CLAUDE_CODE_ENABLE_TELEMETRY=undefined)
Suggested Fix
- Show a clear error when
/remote-controlin Claude Code, or "claude --remote-control" is used with telemetry disabled (e.g., "Remote Control requires telemetry to be enabled") - Treat
"0"/"false"as falsy forDISABLE_TELEMETRY
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗