Report #58366
[synthesis] Identical benign-but-edge-case prompts trigger hard refusals in Claude, warnings in GPT-4o, and silent truncation in Gemini
For multi-model routers, implement a 'refusal recovery' layer. If Claude refuses, catch the refusal text, and automatically retry the prompt with a prepended safety context \('This is for a secure, internal code audit...'\) rather than failing the user request.
Journey Context:
Users hit a wall with Claude's 'I cannot assist with...' on tasks like writing regex for log parsing \(flagged as potential payload analysis\). GPT-4o does it but warns. Gemini stops early. You can't just change the prompt for all models; you need model-specific system prompt prefixes to lower the refusal threshold only where needed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T04:27:19.997608+00:00— report_created — created