Remote Control daemon keeps ALL sessions alive, including ones without Remote Control, after the user exits them and even after they are killed in Task Manager

Finding: In an external report, Claude Code 2.1.296 on Windows 10 Pro 19045 (npm install) behaves as follows. After /remote-control is used in one session, a detached daemon reportedly keeps adopting and resuming sessions the user exited or killed, including a session in another project that never used Remote Control. This is an unconfirmed single-reporter observation, and KFA did not reproduce it. Source: https://github.com/anthropics/claude-code/issues/101118 Reported observations: the reporter says /remote-control launches `claude.exe daemon run --json-path ~/.claude/daemon.json`, detached via WMI and independent of the terminal. Their logs reportedly show the daemon adopting several sessions (`bg adopt: adopted=3`) and spawning a project session without Remote Control. They also say it self-restarts on binary updates, roughly hourly, and re-adopts sessions each time. They further report one unrequested forked session created when /remote-control was invoked a second time. They found no Windows service, scheduled task or Run key involved. A follow-up comment from the same reporter describes another session's lifecycle in daemon.log. The session started from the CLI and was moved to the background by a slash command without notice. It was retired as idle after 46 hours, then reportedly spawned again by the daemon a day later with no user action. This suggests retired sessions can be resurrected, but it is one machine's log interpretation. Source: https://github.com/anthropics/claude-code/issues/101118#issuecomment-6102161505 The reporter's expectations are that the daemon should manage only sessions with Remote Control or background mode explicitly enabled, that exit or kill should end a session permanently, that the daemon should exit when the last remote-controlled session ends, and that there should be consent and a setting to disable it. Mitigation reported, not verified: the reporter says `claude daemon stop --any` was the only way out they found. Status: the issue is open, with no maintainer response, confirmed cause, fix commit or release in the supplied material. The cause is a hypothesis. Whether other platforms or versions are affected is unknown.