ccRemoteControlDefaultEnabled: true not honored on restart — Remote Control resets to OFF every time
Bug Description
The ccRemoteControlDefaultEnabled preference in claude_desktop_config.json is set to true, but Claude Code Desktop (CC Desktop) resets Remote Control to OFF every time the app restarts. Users must manually click \"Turn on Remote Control\" for each session after every restart.
Expected Behavior
When ccRemoteControlDefaultEnabled: true is set, Remote Control should automatically be enabled on app startup — for all active sessions, or at minimum for the default/new session — without requiring manual interaction.
Actual Behavior
- Remote Control is always OFF after restart regardless of the
ccRemoteControlDefaultEnabledsetting - The Remote Control state is not persisted to any config or session file on disk
- Every restart requires manual re-enabling per session
Impact
This blocks true automation workflows. If any automated pipeline depends on Remote Control being active (e.g., headless agents sending messages to a CC Desktop session), a simple app restart breaks the entire pipeline and requires manual intervention to restore it.
Environment
- macOS 12.6 (Monterey)
- Claude Code Desktop (CC Desktop)
Config
// ~/Library/Application Support/Claude/claude_desktop_config.json
{
"preferences": {
"ccRemoteControlDefaultEnabled": true,
"chicagoEnabled": true,
"remoteToolsDeviceName": "leisureapplemacbook-local"
}
}
Requested Fix
Either:
- Honor
ccRemoteControlDefaultEnabled: trueand auto-enable Remote Control on startup, OR - Persist the per-session Remote Control state to disk so it survives restarts
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗