[BUG] [CLAUDE DESKTOP] Unsafe default when approval required on DB activity

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude Desktop version:
Claude 1.2581.0 (f10398) 2026-04-14T17:16:40.000Z

This is a UX bug, not a feature req IMO as the current UI is the opposite of what common sense would dictate, and can cause security issues.

In Claude Desktop, when there are restrictions on a connector (eg: Supabase in my case) that require "Approval", the default should be "Allow Once", not "Allow Always".

It's too easy to press [enter] by accident and disable the approval-requirement.

From a UX perspective, if I've gone to the effort of adding the requirement for approval, then the DEFAULT behaviour is... to require approval, not to wave it away "forever". I know I can go reset it again in the connector config, so not "forever", but hopefully you know what I mean.

TBH, I am not even sure if "Allow Always" is even an option that should be presented in that part of the UI. If one wants to do that, one can change the connector config setting.

Basically the UI does not reflect the expected default behaviour of the feature.

Cheers.

What Should Happen?

In Claude Desktop, when there are restrictions on a connector (eg: Supabase in my case) that require "Approval", the default should be "Allow Once", not "Allow Always".

Error Messages/Logs

Steps to Reproduce

• Enable "Needs approval" in the connector config
• request Claude to do the thing that requires the approval
• Observe the behaviour of the approval dialogue

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

1.2581.0

Platform

Other

Operating System

Windows

Terminal/Shell

Other

Additional Information

This form is not very well-suited for raising Claude Desktop issues (asking for Claude Code versions, terminal versions, etc). I get that this is the claude code repo, but this is where we are directed by "Fin" to raise Claude Desktop issues, and I can find no better place to do so. I also note other ppl have raised CD issues here, so I guess it's OK.