[BUG] Remote Control: sessions started from the Android app ignore settings.json permissions.defaultMode=bypassPermissions and run in auto mode (CLI-started sessions honour it)

Summary

Sessions of a claude remote-control server that are started from the Android app ignore permissions.defaultMode: "bypassPermissions" from settings.json and run in auto mode (the "auto mode classifier" decides / denies tool calls). The same server, same settings, when a session is started/resumed from the CLI on the host, honours bypassPermissions as expected.

Environment

• Claude Code 2.1.232 (also seen on 2.1.231); native binary ~/.local/bin/claude
• Ubuntu 24.04 (also on 22.04 before today's upgrade), running as a systemd service
• Server command: claude remote-control --capacity 16 (no --permission-mode flag; relies on settings)
• Client: Claude Android app (Remote Control → start a new session on this server). Web client behaves the same as the app in my observation.

Settings

Both user settings (~/.claude/settings.json, and the per-account CLAUDE_CONFIG_DIR=~/.claude-2/settings.json) and project settings (<cwd>/.claude/settings.json) contain:

{
  "permissions": { "defaultMode": "bypassPermissions" },
  "skipDangerousModePermissionPrompt": true,
  "remoteControlAtStartup": true
}

Expected

A remote-control session started from the app runs with bypassPermissions (as configured), i.e. no auto-mode classifier gating.

Actual

Tool calls in app-started sessions get:

Permission for this action was denied by the Claude Code auto mode classifier. Reason: Blocked by classifier. ...
To allow this type of action in the future, the user can add a Bash permission rule to their settings.

The classifier ends up denying ordinary read-only commands too (e.g. grep -n "up -d" file.js, ls, writing a file with the Write tool) once the conversation contains phrases like "ignore the classifier", so an admin-style session (system upgrade follow-up: apt, editing /etc/apt/sources.list.d, restarting units) becomes impossible to finish from the app.

Starting the session from the CLI on the same host with the same settings → bypassPermissions is applied and no classifier is involved.

Related

• #29214 (mobile app shows permission prompts despite --dangerously-skip-permissions)
• #71518 (--permission-mode bypassPermissions ignored on mobile, closed)
• #31908 (feature: combine remote-control with --dangerously-skip-permissions)

This report is about the settings.json defaultMode path (no CLI flag), which works for CLI-started sessions but is not applied to app-started sessions of the same server, so it looks like the bridge/app session creation overrides the configured mode with auto mode.