ChatGPT URL Fetch Degradation: Direct Request Works, Protocol Request Fails

TECHNICAL FINDING

TL;DR: ChatGPT can fetch immutable GitHub URLs when asked directly, but refuses or reports inability when the same URLs are presented as part of a formal verification protocol. This appears to be a behavior change that occurred between early July and mid-July 2026, with no documented announcement.

Background:

I built a course delivery system that relies on AI assistants reading specific files from GitHub at immutable commit-pinned URLs. In early July, ChatGPT, Claude, and Meta AI all succeeded. As of mid-July, ChatGPT fails in a specific way: it can fetch the URL individually but refuses when that fetch is part of a protocol.

The Contradiction:

Test A (direct request): "Fetch URL X and read the first line"

Result: ChatGPT fetches successfully and reports correctly

Test B (protocol request): Same URL in a verification gate with steps like "Fetch these immutable URLs, verify the release ID, produce a receipt"

Result: ChatGPT reports inability to fetch and refuses to proceed

Questions:

Has anyone else experienced this specific contradiction?
Are you aware of any ChatGPT behavior changes around URL handling or verification protocols in mid-July?
Have you tested systems that depend on "AI reads this URL"? Do they still work?

I've documented reproducible tests that any engineer can run. Full technical report with step-by-step procedures available if interested. I'm hoping I'm wrong about this, but the contradiction is consistent and repeatable.

My notes are here:

https://github.com/agentforgeframework-cpu/-deepresearch-reports/blob/main/share-docs/AI-URL-FETCH-DEGRADATION-FINDINGS.md

4 comments

ChatGPT URL Fetch Degradation: Direct Request Works, Protocol Request Fails