[Bug] Opus 5.5 false-positive flagging of QSAR toxicity modeling work

Open
#111,490 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Domain
ai, security

Research direction

This is a report about the safety classifier flagging legitimate QSAR toxicity modelling, not about a file in the repository — the body names no source path, only the platform (win32), terminal (windows-terminal), version 2.1.327 and Feedback ID 22060a26-0912-423c-9620-c1e7ec0ca8b5. Start by pulling the feedback record for that ID and reproducing the flagged prompts, then determine whether the trigger is prompt wording, the open-source QSAR context, or the model version. Done means a triage answer explaining what the reporter can change and, if the flag is wrong, a routing to whoever owns classifier tuning; the reporter's own question ('can I do something to avoid being flagged') is the acceptance criterion, and no behaviour change is verifiable from the issue alone.

Written by the indexing model from the issue text.

Description

area:model bug platform:windows

Bug Description
opus 5.5 flags sometimes my work, forcing the change to older models. I'm working on QSAR models for human and eco toxicity, often applied to drugs, on software that is released as open source on GitHub, there's surely nothing illegal nor dangerous in my work. I'd be happy to know if I can do something to avoid being flagged

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.327
  • Feedback ID: 22060a26-0912-423c-9620-c1e7ec0ca8b5
Dominant language
TypeScript
Stars
156k
Forks
25k
Avg merge
16h 19m
Merged PRs (30d)
5

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from anthropics/claude-code

All issues in anthropics/claude-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.