Approving a plan from a remote session drops out of auto mode despite useAutoModeDuringPlan: true

Summary

When a plan is approved from a remote session (Remote Control / claude.ai-code), the session drops out of auto permission mode into default (manual prompts) — even with useAutoModeDuringPlan: true set and loaded. Because the permission-mode toggle (Shift+Tab) requires the local terminal, the session cannot be returned to auto remotely, so it's effectively stuck requiring manual approvals until the user is physically at the machine.

Environment

• Claude Code v2.1.162
• Platform: Linux
• ~/.claude/settings.json:
• permissions.defaultMode: "auto"
• useAutoModeDuringPlan: true
• remoteControlAtStartup: true

Steps to Reproduce

1. Start a fresh session (so settings.json is loaded). Confirm auto mode is active.
2. Have Claude enter plan mode and present a plan via ExitPlanMode.
3. Approve the plan from a remote session (claude.ai/code or mobile).
4. Observe the next tool call (e.g. a Write).

Expected

With useAutoModeDuringPlan: true and defaultMode: "auto", execution after plan approval continues in auto mode (no manual permission prompt).

Actual

The next tool call triggers a manual permission prompt — the session has dropped to default mode. It cannot be switched back to auto from the remote session (Shift+Tab is local-terminal only), so the session is blocked on manual approvals until the user returns to the physical machine.

Notes

• Verified useAutoModeDuringPlan: true was present and valid JSON, and the session was started after the setting was added (config confirmed loaded).
• Reproduced twice; the first attempt was inconclusive because the setting had been edited mid-session, but a clean fresh-session retest still failed.
• Impact: makes remote/away workflows unusable for plan-based tasks — the whole point of approving plans remotely is undercut if every subsequent action then blocks on a local prompt.