[Bug] Scheduled tasks ignore Remote Control default settings and start with remote control disabled
Bug Description
Scheduled tasks (routines) in Claude Desktop never start with Remote Control enabled, even with both defaults turned on:
- claude_desktop_config.json → preferences.ccRemoteControlDefaultEnabled: true
- ~/.claude/settings.json → remoteControlAtStartup: true
Every scheduled run starts with remoteControlState "off" (checked across 8 routines, Linux desktop app). The only workaround is turning the toolbar switch on by hand in each run, after it has already started.
It also can't be done from inside the run: mcp__ccd_session_mgmt__set_remote_control is blocked in unattended sessions ("unavailable in unattended sessions"), and it refuses unattended sessions as a target when called from another session. The scheduled-task API (update_scheduled_task) has no Remote Control option either.
Request: apply the Remote Control default to scheduled runs, or add a per-routine "start with Remote Control" option. My routines prepare drafts that I review and approve from my phone, so without Remote Control I can't act on them until I'm back at the computer.
Environment Info
- Platform: linux
- Terminal: tmux
- Version: 2.1.281
- Feedback ID: c46c443f-8f0c-4bbf-bc61-71f6695848e7
3 Comments
Same on macOS (Claude desktop 2.9939.2), so it isn't Linux-only. Looks like the same root cause as #92296.
remoteControlAtStartup: truein~/.claude/settings.json. Sessions I start myself connect automatically.remoteControlState: "off", andPushNotificationfrom the run returnsMobile push not sent (Remote Control inactive).set_remote_controlis refused by a PreToolUse hook:This tool is unavailable in unattended sessions (scheduled-task runs and remote-dispatched trees).spawn_taskchip from the run shows only in the run's own session on the desktop. A session started from it does connect, but only after someone clicks it at the desk.So a routine that finds something needing a decision overnight can't reach the phone at all. Scheduled runs are the sessions that most need Remote Control, since nobody is at the desk when they run. A per-user or per-task option to connect scheduled runs would fix it.
For cross-reference, the same behaviour is reported in:
remoteControlState: "off", so push notifications never reach the phoneAlso related: #96220 (Remote Control lost after restart, and
set_remote_controlrefused in unattended sessions) and #91992, which asks for the opposite (opt scheduled sessions out). A per-routine "start with Remote Control" setting would satisfy both.Anthropic support confirmed this via ticket (2026-09-28): scheduled-task sessions starting as local sessions with no Remote Control connection and no phone push is "expected today," there is no setting to change it, and it's been passed to the internal team with no timeline. The only offered workaround is running the routine as a cloud task instead — which doesn't help anyone whose routine needs local files or a local app, which is presumably most of what's driving this report.