claude remote-control --permission-mode bypassPermissions is silently ignored on mobile (native Windows)

Scenario

claude remote-control (alias claude remote) accepts --permission-mode bypassPermissions, and the flag is listed in claude remote-control --help. Starting a server-mode remote session with it and connecting from the Claude iOS app does not suppress permission prompts.

Steps to reproduce

1. On the local machine, start a remote-control session in bypass mode:

``bash
claude remote-control --permission-mode bypassPermissions --name msi-happy-github
``

1. Open the Claude iOS app → Code tab → tap the session (msi-happy-github) to connect.
2. Send a prompt that triggers a tool call, e.g. create a file test.txt with "hello" then run "type test.txt".
3. Observe the iOS app when Claude reaches the edit / bash step.

Expected

No permission prompts on the mobile client — bypassPermissions is honored for the remote session, matching the flag set at startup.

Actual

The iOS app prompts for approval on every file edit and bash command. The --permission-mode bypassPermissions flag is silently ignored: accepted by the CLI parser, no effect on the connected client.

If the flag can be set for a remote session, it should work. Either honor it, or reject/remove it — silently accepting a flag that does nothing is the worst outcome.

Environment

• Claude Code: v2.1.193
• OS: Windows 11 Home (26200) — native Windows, not WSL
• Client: Claude iOS app
• Plan: subscription (claude.ai OAuth login)
• No managed-settings policy and no permissions.defaultMode override present — the flag is simply not propagated.

Notes

• Related to #29214 (reported on WSL). This adds a native-Windows repro and the case for the CLI contract: --permission-mode is in claude remote-control --help, so accepting it without effect is a bug regardless of platform.
• Suggested fixes (either is fine):
• Propagate the local session's permission mode to the remote client, or
• If bypass-over-remote is intentionally disallowed, reject the flag at startup with a clear error instead of silently ignoring it.
• Related UX gap: the mobile mode selector doesn't expose a "Bypass permissions" option (#47172).