Completely irrational Astra refusal doesn't let me switch to Daybreak Blue
Open
Nobody has claimed this yet.
bug
model-behavior
safety-check
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
I have access to Daybreak Blue. I am verified. Astra was for the n-th time blocked by a cyber_policy refusal.
But it gets worse. Now it even REFUSES TO SWITCH TO THE AUTHORIZED MODEL.
This is beyong stupidity and is breaking my entire workflow. For Christ's Sake, your guardrail classifier is broken. Fix it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified. Start by reviewing the Astra refusal, the attempted switch to Daybreak Blue, and the attached screenshot, then determine where this behavior can be reproduced. Done means an authorized switch succeeds after the refusal without blocking the workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100