claude-code - 💡(How to fix) Fix [Feature Request] Lock permission dropdown in bypassPermissions mode to prevent accidental changes [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47766Fetched 2026-04-15 06:42:57
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

Problem

When using claude remote-control --permission-mode bypassPermissions, the permission dropdown button ("Bypass permissions ⌄") is placed directly next to the text input area in both the desktop and mobile Claude apps.

It's very easy to accidentally click/tap on it while typing, which opens a menu with three options (Ask permissions / Auto accept edits / Plan mode). If you accidentally select one, the session loses bypassPermissions and there's no way to restore it without restarting the remote-control session.

This is especially frustrating on mobile where the tap target is close to the keyboard area.

Expected behavior

When a session is started with --permission-mode bypassPermissions, the permission dropdown should be locked/disabled so it cannot be accidentally changed. Or at minimum, add a confirmation dialog before downgrading from bypass mode.

Steps to reproduce

  1. Start claude remote-control --name test --permission-mode bypassPermissions
  2. Connect via Claude app (desktop or mobile)
  3. While typing in the input box, accidentally click/tap the "Bypass permissions" button
  4. Permission mode is silently downgraded — no way to restore without restarting

Suggested solutions (any of these would help)

  • Disable/hide the dropdown when bypassPermissions is set via CLI
  • Add a confirmation dialog: "Are you sure you want to change permission mode?"
  • Add a way to restore bypass mode from the UI without restarting

extent analysis

TL;DR

Disable or hide the permission dropdown when --permission-mode bypassPermissions is set via CLI to prevent accidental mode changes.

Guidance

  • Consider adding a confirmation dialog before allowing changes to the permission mode to prevent accidental downgrades from bypassPermissions.
  • Evaluate the UI/UX to ensure sufficient spacing between the text input area and the permission dropdown button to reduce accidental clicks/taps.
  • Investigate adding a feature to restore bypassPermissions mode from the UI without requiring a restart.
  • Review the mobile app's design to ensure the tap target for the permission dropdown is sufficiently distant from the keyboard area to minimize accidental selections.

Example

No code example is provided as the issue does not specify the technology stack or implementation details.

Notes

The solution should be implemented in a way that does not introduce new usability issues or contradictions with existing functionality. It's also important to consider the trade-offs between security, usability, and the specific requirements of the bypassPermissions mode.

Recommendation

Apply a workaround by disabling or hiding the permission dropdown when --permission-mode bypassPermissions is set, as this directly addresses the issue of accidental mode changes without introducing new complexity.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

When a session is started with --permission-mode bypassPermissions, the permission dropdown should be locked/disabled so it cannot be accidentally changed. Or at minimum, add a confirmation dialog before downgrading from bypass mode.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING