Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Remote control mode selector missing "Bypass permissions on" option [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#47172•Fetched 2026-04-13 05:39:32
View on GitHub
Comments
0
Participants
1
Timeline
5
Reactions
0
Author
davjmv85davjmv85
Participants
davjmv85davjmv85
Timeline (top)
labeled ×4unlabeled ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

No response

Section/Topic

Remote Control / Permission modes

Current Documentation

The documentation describes three permission modes available via Shift+Tab in the terminal: "Accept edits on", "Plan mode on", and "Bypass permissions on". However, there is no mention that the mobile/web app remote control only exposes two of the three modes.

What's Wrong or Missing?

The remote control mode selector in the mobile/web app only shows "Plan" and "Code". The "Bypass permissions on" option is missing. If a user has Bypass permissions active from the terminal and switches to Plan from the mobile app, they cannot return to Bypass permissions — the option doesn't exist in the selector. This effectively locks them out of a mode they had active.

Suggested Improvement

  1. Add "Bypass permissions on" as a third option in the remote control mode selector (mobile/web app) 2. The mode selector should match the three options available via Shift+Tab in the terminal: Accept edits on, Plan mode on, Bypass permissions on 3. Document that the remote control UI supports all three permission modes

Impact

High - Prevents users from using a feature

Additional Context

No response

extent analysis

TL;DR

Adding "Bypass permissions on" as a third option in the remote control mode selector for the mobile/web app is likely the most straightforward fix.

Guidance

  • Review the current implementation of the remote control mode selector in the mobile/web app to understand why "Bypass permissions on" is not included.
  • Compare the permission modes available via Shift+Tab in the terminal with those in the mobile/web app to ensure consistency.
  • Consider updating the documentation to reflect the current limitations of the remote control UI and the steps users can take if they are locked out of a mode.
  • Evaluate the feasibility of adding the missing "Bypass permissions on" option to the remote control mode selector.

Example

No code snippet is provided as the issue does not include specific implementation details.

Notes

The solution may require updates to both the mobile/web app's UI and the underlying logic that handles permission modes, as well as documentation changes.

Recommendation

Apply workaround: Add "Bypass permissions on" as a third option in the remote control mode selector, as this directly addresses the reported issue and prevents users from being locked out of a mode they had active.

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…
#permission error#memory optimization#batch processing#GPU compatibility#latency issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [DOCS] Remote control mode selector missing "Bypass permissions on" option [1 participants]