Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] [CLAUDE DESKTOP] Unsafe default when approval required on DB activity [6 comments, 3 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#48409•Fetched 2026-04-16 07:00:58
View on GitHub
Comments
6
Participants
3
Timeline
14
Reactions
1
Author
dacameron-proactivedacameron-proactive
Participants
AlexanderBolshakovAlexanderBolshakovdacameron-proactivedacameron-proactivegithub-actions[bot]github-actions[bot]
Timeline (top)
commented ×6labeled ×2closed ×1cross-referenced ×1

Error Message

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • 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.

extent analysis

TL;DR

The default approval behavior in Claude Desktop should be changed to "Allow Once" instead of "Allow Always" when a connector requires approval.

Guidance

  • Review the connector configuration settings to understand how the approval requirements are currently implemented.
  • Consider modifying the UI to reflect the expected default behavior of requiring approval, potentially by removing the "Allow Always" option or making "Allow Once" the default.
  • Test the approval dialogue behavior with different connector configurations to ensure the desired behavior is achieved.
  • Evaluate whether the "Allow Always" option is necessary in the approval dialogue, and if not, consider removing it to prevent accidental overrides of approval requirements.

Example

No code snippet is provided as the issue is related to UI behavior and configuration.

Notes

The issue is specific to Claude Desktop and its interaction with connectors that require approval. The solution may involve changes to the UI or the underlying configuration settings.

Recommendation

Apply a workaround by carefully reviewing and configuring the connector settings to ensure the desired approval behavior, as the current UI behavior may not be easily modifiable.

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…
#ISR setup#authentication setup#request error#file not found#serialization error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING