Add auto-enable option for /remote-control
Resolved 💬 3 comments Opened Apr 3, 2026 by ithiria894 Closed Apr 7, 2026
Feature request
Add a way to automatically enable /remote-control on every session start, without having to type it manually each time.
Suggested approaches (any would work)
- settings.json key:
"remoteControl": "always"or"autoRemoteControl": true - CLI flag:
claude --remote-controlthat starts an interactive session with remote control already active /configtoggle: "Enable Remote Control for all sessions"
Why
Power users who always want remote access (e.g., monitoring sessions from mobile) currently have to type /remote-control at the start of every session and every /resume. There's no way to persist this preference.
What I tried
- Searched settings.json schema —
remotekey only hasdefaultEnvironmentIdfor SSH environments - Searched CLI flags — no
--remote-controloption exists - SessionStart hooks can't invoke slash commands, so a hook-based workaround isn't possible
- The runtime state (
isRemoteMode) is not persisted or configurable
Environment
- Claude Code v1.0.33 (CLI, Linux)
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗