Cache

You might say

The new styles are deployed, but some people still see the old version. Find out which cache layer has not updated.

Keep reusable results so later requests do not always return to the originWhen new CSS is deployed but an old style remains visible, the browser, a shared cache, or a CDN may still be reusing an older copy. Caching reduces waiting and repeated transfer; diagnose the layer that served the old result, because clearing one browser does not prove a shared cache or origin has changed.

You can say this to an AI Agent

Ready to paste into Cursor, Claude Code, or Codex
Structured AI Agent prompt

Find out whether this old CSS comes from the browser cache, a CDN/shared cache, or the origin. Check the resource URL, response headers, and requests from different locations. Then invalidate the old copy or update the resource address as appropriate, and verify both local and external requests. Do not treat Browser Storage as the cache diagnosis.

Want your Agent to translate plain-language UI ideas automatically?Install free VibeHub Skill →
Further reading