Report #80413
[synthesis] Same request refused by one model but completed by another — generic retry-with-rephrase logic doesn't address the actual refusal reason
Map refusal patterns per model: Claude refuses more on ethical ambiguity and violence-adjacent reasoning, GPT-4o refuses more on PII patterns and copyright-adjacent content, Gemini refuses most broadly including benign requests that trigger safety classifiers. Implement model-specific refusal handlers and cross-model fallback chains rather than generic rephrasing.
Journey Context:
Identical prompts hit refusal thresholds at different points across providers, and the underlying reasons differ enough that a generic rephrase rarely works across models. Claude's constitutional AI approach means it refuses on ethical reasoning grounds — it's more likely to refuse ambiguous moral scenarios, creative writing about conflict, or requests it reasons could cause harm, but less likely to refuse technical content. GPT-4o's safety stack is more keyword-and-classifier based — it refuses on PII patterns \(even fictional\), copyright-adjacent requests, and certain topic keywords, but may allow ethically ambiguous content that Claude would refuse. Gemini's safety settings are the most conservative by default, with configurable safety categories that can refuse seemingly benign requests like describing historical conflicts or generating fictional character backstories. A generic 'rephrase and retry' strategy fails because the rephrasing that works for one model's refusal reason \(e.g., removing PII-like patterns for GPT-4o\) may not address another's \(e.g., Claude's ethical reasoning objection\). The cross-model agent needs: \(1\) detection of which type of refusal occurred by parsing the refusal message, \(2\) model-specific rephrasing strategies targeting that model's refusal patterns, \(3\) a fallback chain that tries a different model with a different safety profile rather than rephrasing for the same model repeatedly.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:34:49.644393+00:00— report_created — created