claude-code - 💡(How to fix) Fix Plan mode does not restrict tool access when controlling a desktop session via remote control from mobile

Summary

When using Claude Code mobile to remote-control a desktop Claude Code session, switching the mobile client into plan mode does not actually restrict the underlying agent's tool access. The agent retains Write/Edit (and presumably other write-capable tools) and will perform file modifications during what the mobile UI presents as plan mode.

Reproduction

1. Have a Claude Code session running in VS Code on a desktop (Windows 11 in this case).
2. From Claude Code mobile, remote-control that desktop session.
3. Switch the mobile client into plan mode.
4. Continue the conversation. The agent has Write/Edit available and will modify files in the workspace and elsewhere when asked to.

Expected

Plan mode should restrict the agent to read-only operations regardless of which client the user is interacting through. Remote-controlling a desktop session from mobile in plan mode should be the same as being in plan mode locally.

Actual

The agent has full write tool access throughout. From the agent's side there is no visible plan-mode indicator and no restriction on Write/Edit tool calls. Files are created and modified normally.

Likely interaction

The mode state set on the mobile client during a remote-control session does not appear to propagate to constrain the desktop agent's tool access. The mode change is presented in the UI but has no effect on the underlying agent.

Environment

• Mobile: Claude Code mobile (plan mode)
• Desktop: Claude Code in VS Code on Windows 11
• Same conversation, controlled remotely from mobile