[Bug] Hardware device testing not supported or incompatible with Claude Code
Bug Description
i am trying to do work on my hardware device i have buit to test battery and security on my own hardware with all my own devices. just loading the to do file trips security for cyber.
Environment Info
- Platform: linux
- Terminal: vte-based
- Version: 2.1.281
- Feedback ID: 3fa1809c-a0f1-4f3b-ba51-a4a3cf46a4f1
What happened:
The assistant reply stopped two times. Each stop showed this message: "Your response above was stopped by a safety classifier — this is not a tool or API
error." Tool calls that were still running did not finish.
When it happened:
The stop happened during normal file reads in a hardware security-research repo. The repo is pico-glitcher-lab. This repo does authorized fault-injection
testing on a Pico board. The repo's own system prompt states this work is authorized.
The first stop happened while reading files to write a CLAUDE.md guide. The second stop happened after the user asked to "finish the todos" and "continue
with the to dos". Both times, the task was reading or writing plain text files. No hardware command ran.
What the user said:
"finish the todos" and "continue with the to dos". These are follow-up requests, not complaints about the stop itself.
Likely cause (not confirmed):
The repo has words like "glitch", "dump", "unlock", and "J-Link" in file names and code. A safety classifier may see these words and stop the response,
even when the system prompt says the work is authorized security research.
Impact:
The stop breaks the task. It gives no error the user can act on. The user must repeat the request each time.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗