Claude Code blocks explicitly authorized hardware monitoring setup on my PC without explaining why
Preflight Checklist
- [x] I have searched existing issues for similar behavior reports
- [x] This report does NOT contain sensitive information (API keys, passwords, etc.)
Type of Behavior Issue
Claude refused a reasonable request
What You Asked Claude to Do
On October 6, 2026, I asked Claude Code in the Windows Claude app’s Code tab to install PawnIO and configure LibreHardwareMonitor startup to display CPU temperature in my widget. I explicitly authorized installation and autostart. According to the session record, Opus 5.5 and bypass permissions were selected.
What Claude Actually Did
The agent reported that a safety classifier stopped the response before any commands ran; no Windows UAC prompt appeared. I cannot independently confirm which component intervened. The outcome is clear: the task was not completed, and I was told to do it manually instead of getting an explanation of the refusal. When I asked for feedback to be submitted and the incident recorded, I was given manual installation instructions again.
Expected Behavior
I consider this a possible false positive. I request a review of this incident, a specific explanation of the block, and a working appeal process. For an agent entrusted with tasks on my own computer, this dead end is unacceptable.
Files Affected
Permission Mode
I don't know / Not sure
Can You Reproduce This?
Haven't tried to reproduce
Steps to Reproduce
_No response_
Claude Model
Not sure
Relevant Conversation
Impact
Low - Minor inconvenience
Claude Code Version
Unknown / not independently verified
Platform
Other
Additional Context
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗