Bug Description
The "Enable Remote Control for all sessions" setting in /config repeatedly resets to false, even though the underlying config file (~/.claude.json) has "remoteControlAtStartup": true.
Every new session starts with Remote Control disabled. The user must manually re-enable it each time via /config.
Steps to Reproduce
- Open Claude Code
- Run
/config
- Toggle "Enable Remote Control for all sessions" to
true
- Close the session
- Start a new Claude Code session
- Run
/config again
- Observe: "Enable Remote Control for all sessions" is back to
false
Expected Behavior
The setting should persist across sessions. Once enabled, Remote Control should remain enabled for all subsequent sessions.
Actual Behavior
The setting resets to false on every new session, despite ~/.claude.json containing:
{
"remoteControlAtStartup": true
}
There appears to be a desync between the persisted file value (true) and what the /config UI reads at startup (false).
Environment
- Claude Code version: 2.1.63
- OS: macOS 26.3 (Tahoe)
- Install method: native (
"installMethod": "native" in ~/.claude.json)
- Auto-updates: disabled (
"autoUpdates": false)
- Plan: Claude Max (Opus 4.6)
Additional Context
Feature Request (if by design)
If the setting intentionally doesn't persist, please consider adding:
- A CLI flag (e.g.,
claude --remote-control) to start with RC enabled
- Or an environment variable (e.g.,
CLAUDE_REMOTE_CONTROL=1) for shell profile integration
Bug Description
The "Enable Remote Control for all sessions" setting in
/configrepeatedly resets tofalse, even though the underlying config file (~/.claude.json) has"remoteControlAtStartup": true.Every new session starts with Remote Control disabled. The user must manually re-enable it each time via
/config.Steps to Reproduce
/configtrue/configagainfalseExpected Behavior
The setting should persist across sessions. Once enabled, Remote Control should remain enabled for all subsequent sessions.
Actual Behavior
The setting resets to
falseon every new session, despite~/.claude.jsoncontaining:{ "remoteControlAtStartup": true }There appears to be a desync between the persisted file value (
true) and what the/configUI reads at startup (false).Environment
"installMethod": "native"in~/.claude.json)"autoUpdates": false)Additional Context
~/.claude.jsonfile correctly contains"remoteControlAtStartup": true— the value is being written but not read back (or overridden at startup)."autoUpdates": falseis set, so this is not caused by an auto-update overwriting the file.Feature Request (if by design)
If the setting intentionally doesn't persist, please consider adding:
claude --remote-control) to start with RC enabledCLAUDE_REMOTE_CONTROL=1) for shell profile integration