claude-code - 💡(How to fix) Fix [BUG] CC asks to approve commands/scripts without showing what is to be approved [1 participants]

Official PRs (…)
ON THIS PAGE

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#52760Fetched 2026-04-24 10:40:16
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Participants
Timeline (top)
labeled ×4

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?

<img width="2151" height="652" alt="Image" src="https://github.com/user-attachments/assets/6bc1a7f8-ac3c-46a5-87dc-fc6cafa970f6" />

What Should Happen?

it should alwasy display what is to be approved

Error Messages/Logs

Steps to Reproduce

let it run

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.84

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue might be resolved by checking the compatibility of the current Claude Code version with the Anthropics API or reviewing the approval display logic.

Guidance

  • Review the release notes of Claude Code version 2.1.84 to see if there are any known issues or changes related to the approval display.
  • Check the Anthropics API documentation to ensure that the API endpoints and parameters used by Claude Code are correct and compatible with the current version.
  • Since this is a regression, compare the code changes between the current version and the last known working version to identify potential causes.
  • Verify that the issue is not specific to the macOS or Terminal.app environment by testing on a different platform or terminal.

Notes

The lack of error messages or logs makes it difficult to pinpoint the exact cause, and without more information about the last working version, it's challenging to provide a more specific solution.

Recommendation

Apply workaround: Given the regression nature of the issue and the absence of explicit error messages, attempting to workaround the problem by reviewing compatibility and code changes seems like the most prudent step before considering any upgrades or more invasive changes.

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…

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 [BUG] CC asks to approve commands/scripts without showing what is to be approved [1 participants]