[Bug] Safety filter blocks legitimate internal documentation/demo content

Status Open
Reported on v2.1.283
Maintainer reply None cached
Activity 0 comments · opened Sep 30, 2026

Bug Description
Response stopped by the safety check during legitimate internal demo work.

What I was doing: building an internal HTML walkthrough page to show my developer team how I do AI-driven manual QE testing. The page
already covered real work from the same day: creating a sold-out test course session in our TEST environment using two of our automation
repos, then adding it to our golden test data (QE-9098, qe-golden-test-data MR !3).

What I asked for: rework the page around a hypothetical example ticket, clearly labelled as made up, whose acceptance criteria describe
how a sold-out session should appear on the course page. Its only purpose was to walk the devs through how I would test it. No real Jira
ticket was to be created, nothing was to be posted anywhere, and the page is private to me.

What happened: Claude's response was stopped partway through writing the HTML file. Afterwards Claude could not finish or retry that
version, even after I explained it was for an internal demo.

Why I think it's a false positive: the content was a labelled hypothetical, for internal training, about our own product and test data. It
impersonates no one and misleads no one.

Impact: I lost the version of the demo I wanted and had to fall back to an earlier one.

---

Leave the transcript off unless you've checked it's fine to share. The session contains internal system details and log text.

Environment Info

  • Platform: win32
  • Terminal: vscode
  • Version: 2.1.283
  • Feedback ID: 46dbdbc5-9edf-474a-85a3-4cc32a87ecc7

Errors

[]

View original on GitHub ↗