Mobile/web permission dropdown can knock a session out of bypassPermissions with no way back
Problem
When a session runs in bypassPermissions (started from the desktop app), the permission-mode dropdown in the Claude mobile app only offers Manual / Accept Edits / Plan / Auto. Selecting any of them switches the live session off bypass — but since the dropdown can't select bypass, there is no way to restore it from the phone; you must go back to the PC.
One accidental tap (the dropdown sits right next to the text input) permanently downgrades the session's mode from mobile.
Expected behavior
Preferred: add Bypass permissions to the mobile/web dropdown, at least for sessions that already run in that mode. For users who work in bypass mode as their default, the phone currently can only break the mode, never use it.
Alternatively: lock the dropdown while the session is in bypassPermissions, or let the dropdown restore the mode the session started with.
Environment
- Windows 11 desktop app hosting the session, Android Claude app steering it via Remote Control
- Reproduced 2026-07-22
Previously reported as #47766, which was closed as stale and locked without a fix; its closing note asks for a new issue referencing it.
3 Comments
Same here, with a
claude remote-controlserver (the app's "Remote Control" group, sessions created with +).claude remote-control --permission-mode bypassPermissionsdoes start spawned sessions in bypass mode (the app shows "Accept edits" at first, then switches to "Bypass permissions" after the first message).--allow-dangerously-skip-permissions.claude remote-controlrejects that flag (Error: Unknown argument: --allow-dangerously-skip-permissions).Request: support
--allow-dangerously-skip-permissions(or an equivalent setting) inclaude remote-control, and show "Bypass permissions" in the app's picker for sessions that report it available.Claude Code 2.1.260, Linux (LXC), remote-control running as a systemd user service.
Same on v2.1.270, Linux. Host runs
claude remote-control --permission-mode bypassPermissionsas a systemd unit and~/.claude/settings.jsonhasdefaultMode: bypassPermissions. A session opened from claude.ai/code still starts in whatever the dropdown sends (auto here), and the dropdown offers no bypass entry, so the host flag has no effect at all. The docs confirm the dropdown never shows bypass for Remote Control. Either honour the host mode as the session mode or reject the flag at startup; silently ignoring it is the worst of the optionsyess has this been fixed yet??