[BUG] Claude.app-spawned Code sessions ignore remoteControlAtStartup in settings.json

Summary

Claude Code sessions launched by the Claude desktop app (Code tab, Dispatch's start_code_task, etc.) do not activate remote control on startup, even when ~/.claude/settings.json has "remoteControlAtStartup": true. Sessions launched from a terminal using the claude CLI do activate it — the startup banner reads /remote-control is active · Code in CLI at https://claude.ai/code/session_….

Environment

| Component | Version |
|---|---|
| macOS | 26.5 (Build 25F5053d) |
| Claude.app | 1.3109.0 |
| Claude Code CLI | 2.1.114 |

Steps to reproduce

1. Set "remoteControlAtStartup": true in ~/.claude/settings.json.
2. Start a Code session from the Claude desktop app (via the Code tab or an equivalent app-launched path).
3. Compare the startup banner to a claude session launched in the same user account from a terminal.

Terminal-launched session: startup banner shows /remote-control is active · Code in CLI at https://claude.ai/code/session_…

Claude.app-launched session: no remote-control line in the startup banner; session is not discoverable as remote-controllable.

Expected behavior

Both launch paths honor remoteControlAtStartup: true and activate remote control on startup.

Actual behavior

Only terminal-launched sessions honor the setting. Claude.app-launched sessions silently skip remote control activation regardless of the setting value.

Workaround

Send /remote-control as a bare message to the session after it starts. This activates remote control when typed directly in the session prompt.

Related issues

Similar-but-not-duplicate reports about remote control / remoteControlAtStartup behavior:

• #29929
• #37589
• #46317
• #29006