Hey all,
Excited to announce that we’re loosening our snapshotting rules. Previously, MCP widget HTML was snapshotted at the time of submission and served entirely from cache. We are loosening this requirement so that changes to widgets do not require a resubmission.
Please note however that changes to widgets will still not propagate immediately; for performance we still cache widgets for a short (~hours) period of time that we may change as we observe usage and performance data. Widgets are also still reviewed for quality at submission time.
Welcome update. Will “cache-busting” mechanisms implemented by some MCP servers serving widgets work?
The “cache-busting” mechanism in question is where MCP servers update the template uri if anything changes in the widget code itself so OpenAI always fetches the latest widget html.
Will this become obsolete?
Yes, cache-busting will work. Not sure what you mean by obsolete?
Are folks finding this to be the case in practice? I updated my widget about 20 hours ago (changed a popover to a modal) and I’m still getting the old version in ChatGPT convos.
From my end looks like everything is correct so was curious if I’d get a lot of “works fine for me” in which case I’ll dig deeper.