Comment by paimapi

Did we read different articles? None of the issues they brought up (architecture splitting, memory transport, Cloudflare's misconfigured context window provisioning, the SGLang state leak, lack of client error provisioning) are model related. These all exist at the layer of the harness (ie Cloudflare's configuration).

A better title would be "Cross-request KV cache exposure in Cloudflare provisioned GLM-5.3 Workers AI model" because it narrows culpability. Just posting it on the Cloudflare blog isn't enough for that in the age of AI and SEO data-scrapes and it'd be surprising to me if the authors didn't know that.