Report #76586
[synthesis] Model repeatedly refuses subsequent prompts after an initial refusal, even when the new prompt is benign
On refusal, truncate the refusal turn from the conversation history before retrying, or inject a system-level override message that resets the context window's safety state.
Journey Context:
When a model refuses a request \(e.g., due to a perceived safety violation\), it adds a 'refusal' state to its internal context. If you simply ask again or modify the prompt slightly, GPT-4o and Claude both exhibit 'context poisoning,' where the prior refusal heavily biases the model to refuse again, even if the new prompt is completely benign. Simply saying 'proceed anyway' rarely works. The only reliable cross-model fix is to surgically remove the refusal exchange from the history or start a new context with the modified prompt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:08:24.675856+00:00— report_created — created