Remote Control on mobile does not honor settings.local.json wildcards or agent frontmatter permissionMode -- v2.1.119

Summary

Remote Control sessions accessed from the mobile Claude Code app do NOT honor permission settings that work correctly on the desktop CLI. Specifically:

• settings.local.json wildcard allows (PowerShell(), Bash(), Read(), Write(), Edit(*)) are ignored
• Agent frontmatter permissionMode: bypassPermissions is ignored

The mobile Remote Control app wakes users with permission prompts at 3am for PowerShell commands that are explicitly wildcard-allowed at both the project settings level AND the agent definition level.

Environment

• Desktop: Windows, Claude Code v2.1.119
• Mobile: Claude Code iOS app, connected via Remote Control
• Project settings.local.json has: Bash(), Read(), Write(), Edit(), PowerShell(*) in allow array
• Agent MD frontmatter has: permissionMode: bypassPermissions

Expected behavior

Remote Control sessions inherit the same permission context as local CLI sessions. If PowerShell(*) is allowed in settings.local.json and the agent has permissionMode: bypassPermissions in its frontmatter, no permission prompts should fire for PowerShell commands.

Actual behavior

Every PowerShell tool call from a Remote Control session produces a permission prompt on the mobile app. Real example at 3:36 AM local time:

"PowerShell requests permission: Check RAM stamp for build_shaped_v2.py, STEP_2_DECISION.md, process start time, log files"

Options presented: "Allow once" / "Deny" -- no "Allow always" option, and no indication that existing wildcard allows should apply.

Impact

Users running autonomous overnight pipelines rely on Remote Control for mobile check-ins. If every PowerShell call on mobile fires a prompt:

• Users get woken by notifications through the night
• Autonomous operation is defeated -- agent halts waiting for human decision
• Settings configured for the desktop CLI provide zero value for Remote Control
• The gap between "works on my laptop" and "works in the hand" is invisible until production

Reproduction

1. On desktop: ensure settings.local.json has PowerShell(*) in allow array
2. On desktop: ensure agent MD frontmatter has permissionMode: bypassPermissions
3. Launch agent session via local CLI -- confirm no permission prompts for PowerShell
4. Connect via Remote Control from mobile Claude Code app
5. Trigger any PowerShell tool call from the agent
6. Observe permission prompt appears on mobile despite configuration

Request

Remote Control must use the same permission evaluation code path as local CLI. settings.local.json wildcards and agent frontmatter permissionMode must be honored identically on both surfaces.

Related: #37442 (subagent permission inheritance), #36261 (remote session persistence).