[Bug] Scheduled-task sessions don't auto-enable Remote Control on macOS desktop app

Status Open
Reported on v2.1.289
Maintainer reply None cached
Activity 2 comments · opened Oct 9, 2026

Bug Description
Bug: Scheduled-task sessions never auto-enable Remote Control (desktop app, macOS) Summary Since the Claude desktop app update of 3 Sep 2026 (1.40609 -> 1.44121), sessions started by a scheduled task no longer turn on Remote Control automatically, even with "Remote Control on by default" enabled. Interactive sessions still honour the preference. The problem is still present on 2.31226. Impact I run unattended scheduled routines on an always-on Mac mini. I depend on Remote Control to monitor and fix them from my phone. At the moment no scheduled run reaches the phone until someone toggles it on at the Mac, which defeats the purpose. Steps to reproduce 1. Enable Remote Control by default in the desktop app. 2. Create a scheduled task (Code tab) and let it fire with nobody at the machine. 3. Open the Claude mobile app or claude.ai/code. The session isn't there, and Remote Control is "off" for it. Expected A scheduled session honours the Remote Control default, as it did up to 1.40609. The last auto-enabled scheduled run was on 1 Sep 2026. Observed - No "[rcAutoEnable] verdict" line in ~/Library/Logs/Claude/main.log for scheduled sessions after 3 Sep. The verdict seems to be evaluated only on trigger=first_turn / warm_send (a human-sent turn), and a scheduler-started run has neither. - Putting /remote-control in the task prompt has no effect. - PushNotification from within the run returns "Mobile push not sent (Remote Control inactive)". - The set_remote_control session tool is documented as refused for unattended sessions, so the run can't turn it on for itself either. - Tested 9 Oct 2026: a scheduled run calling set_remote_control on itself returns "needs a person's approval, and nobody has opened this scheduled run". After a manual "Run now" of the same routine where I approved the prompt (that run did turn on), the next unattended run of that routine was refused again, so the approval is not stored on the routine the way other tool approvals are. - Toggling it on by hand later works, which shows that sign-in and device enrolment are fine. Request Apply the Remote Control default to scheduled-task sessions, or add a per-task "enable Remote Control" option.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.289
  • Feedback ID: 671efcf2-09e5-4982-b022-ecd45bfdc83f

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗