Permission dialog toggle label is clickable but clicking it changes the value — counterintuitive UX

Resolved 💬 1 comment Opened May 16, 2026 by wainwright1000 Closed Jun 16, 2026

The "Allow this bash command?" dialog has a scope toggle on option 2 that switches between "this session" and "this project (just you)". The toggle is implemented as clickable underlined text embedded in the option label. This creates a serious UX trap:

Steps to reproduce

  1. Trigger a Bash permission prompt.
  2. Read option 2: "Yes, allow <cmd> for this project (just you)".
  3. Decide "this project (just you)" is the desired scope.
  4. Click on the underlined words "this project (just you)" to confirm that choice.
  5. The toggle fires — the label now reads "this session" instead.
  6. The user has accidentally selected the opposite scope.

Expected behaviour

Clicking anywhere on option 2 selects that option with the currently displayed scope. The toggle should be a separate, visually distinct control (e.g. a small inline button or chevron) so that "click to toggle" and "click to select" are clearly different actions.

Actual behaviour

The toggle and the selection target occupy the same element. There is no visual affordance to distinguish them. Clicking the underlined text to confirm your chosen scope switches you to the other one silently.

Suggested fix

Separate the toggle from the selection hit area — for example, a [session | project] pill control to the right of the option text, or simply two distinct option rows (one per scope).

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗