Report #47152
[synthesis] Inconsistent refusals when asking the model to analyze a URL directly
Provide a dedicated \`fetch\_url\` tool rather than relying on the model's native browsing capability; native browsing triggers provider-specific safety filters unpredictably.
Journey Context:
Asking an LLM to 'analyze the content at URL X' yields wildly different refusal thresholds. GPT-4o with native browsing might refuse due to safety filters on the target domain. Claude might refuse to generate code that fetches authenticated sites. Gemini might refuse if the URL looks suspicious. By providing a \`fetch\_url\` tool, the agent delegates the network request to its own sandbox, bypassing the provider's native browsing safety filters and standardizing the refusal logic to the tool's output rather than the model's internal filters.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:37:09.554495+00:00— report_created — created