How ChatGPT dots handles this
A dot keeps working between conversations, so a purge often comes up in the middle of something it is already watching for you. Last week you asked it to keep an eye on your sites, and today you tell it the pricing page on shop changed but still looks old to customers. The dot calls list_sites to match the name, picks a purge type for the change, and runs purge_cache through the xspeedhub app. It brings the result back into the conversation for you to read: the type, the site and how many entries were cleared.
There is nothing to install on the dot itself. OpenAI says plugin permissions are shared across dots, ChatGPT and Codex, so the developer-mode app you created for ChatGPT is the one your dot calls. Check under the dot's Customize, Plugins that xspeedhub is listed before you hand it the job, because OpenAI notes the apps available to a dot may differ. A purge of type all reports the page cache, the object cache and, where Cloudflare is connected in xSpeed, the edge, so the dot can say which store held the stale copy and offer start_preloader as the next step.
Approval on a dot comes from its custom rules, not from xSpeed Hub. Under Customize, Custom rules you describe an action and choose Take action without asking, Take action if pre-approved, Ask before taking action or Hand off to you. Write one that covers purging a cache through xSpeed Hub and set it to Ask before taking action, and the dot stops with a question before purge_cache runs. The Hub has no confirmation step of its own: once a rule lets the dot act, the purge runs as soon as your connection allows writes. For a purge of every site the Hub also tells the dot to say it will touch all of them and wait, which is guidance to the model, not a lock.
Set up ChatGPT dots once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the ChatGPT dots guide.
1Put your sites in xSpeed Hub
Sign in at app.xspeedcache.com with Google or email; the Hub is free and has no site cap. Then connect each WordPress site from its own dashboard: click Connect Hub in the xSpeed Cache top bar, then Connect via xSpeed Hub. Each site needs the free xSpeed Cache plugin.
2Create the xspeedhub app in ChatGPT
In ChatGPT on the web, turn on Developer mode under Settings, Security and login. Open Plugins, select the plus button and create a developer-mode app named xspeedhub with this URL and OAuth. Click Scan Tools, approve access on the xSpeed Hub page that opens, then click Create. If ChatGPT already has the app, skip this step. On a Business workspace only an admin or owner can turn on developer mode and publish the app.
https://app.xspeedcache.com/xspeed/mcp
3Check that your dot can see it
OpenAI says plugin permissions are shared across dots and ChatGPT. Open your dot's profile, then Customize and Plugins, and check that xspeedhub is there. That screen uses the shared ChatGPT settings, and OpenAI notes the apps available to a dot may differ, so confirm it before you hand over a task.
Dot profile > Customize > Plugins > xspeedhub
4Add a custom rule for site changes
Under Customize, Custom rules, describe the action and pick a behavior: Take action without asking, Take action if pre-approved, Ask before taking action, or Hand off to you. Add a rule that covers purging a cache, changing settings or running a speed test through xSpeed Hub, and choose Ask before taking action.
Customize > Custom rules > xSpeed Hub changes: Ask before taking action
Full ChatGPT dots setup, sign-in options and FAQ
Before you send a prompt that changes something
Reads change nothing on your sites, though contact_support emails xSpeed support. Writes run once your connection allows them, so your client's approval prompt and a read-only connection (the token's Read-only everywhere switch, or a Viewer sign-in) are the gates that matter. In a ChatGPT chat, write actions from a developer-mode app need your confirmation by default, and ChatGPT treats a tool without a read-only annotation as a write. xSpeed Hub's tools carry no such annotation. A dot comes with OpenAI's defaults for which actions need approval, and Custom rules let you set, for an action you describe, Take action without asking, Take action if pre-approved, Ask before taking action or Hand off to you. xSpeed Hub has no confirmation step of its own, so a rule that lets your dot act without asking runs a purge or a settings change as soon as your connection allows writes. Keep xSpeed Hub changes on Ask before taking action. For read-only access, sign in as a Viewer member of the workspace; the connection token's Read-only everywhere switch does not apply, because the app signs in with OAuth.
What do I ask?
Three prompts written for ChatGPT dots. More for this job are below.
Use xSpeed Hub to purge the page cache on shop, then tell me in this conversation how many pages were cleared.
With xSpeed Hub, purge only the assets cache on blog after the CSS change, and ask me before you run it.
Ask xSpeed Hub for the cache status of every site first, then propose which ones need a purge. Do not purge yet.
What happens, step by step
A purge throws away stored copies so the next visitor gets a fresh page. Through xSpeed Hub an agent can purge everything, only pages, only CSS and JavaScript assets, the object cache or the REST cache, on one site or across every site in a workspace. A full purge also clears the Cloudflare edge when the site has Cloudflare connected.
01
Find the site
The agent calls list_sites when you have more than one site, then matches the name you used to a site handle. If the name could mean two sites, the Hub tells it to ask you rather than guess.
02
Pick the purge type
purge_cache takes a type: all, page, assets, object or rest. all clears the page cache, the object cache and, when they are connected, the Cloudflare edge and CDN. After a theme or CSS change, assets is enough; after a content edit, page; after a deploy, all.
03
Purge
The call runs straight away on that site once your connection allows writes. For every site at once the agent passes site: "all", and the Hub runs the sites one after another with a one-second pause.
04
Clear only the edge if that is all you need
purge_cloudflare empties the Cloudflare edge cache on its own, without touching the copies on your server. A page or assets purge does not reach Cloudflare; a purge of type all does when Cloudflare is connected.
05
Warm it again
start_preloader rebuilds the cache in the background so the first visitors after the purge are not the ones paying for it.
Reference
| Tool | purge_cache (write) |
|---|---|
| Purge types | all, page, assets, object, rest |
| What all covers | Page cache, object cache, plus the Cloudflare edge and CDN when connected |
| Every site at once | site: "all" or a list of handles, one result per site |
| Fan-out pacing | Sites run one after another with a 1 second pause |
| Edge only | purge_cloudflare, a separate write tool |
| Re-warm | start_preloader after the purge |
| Read-only access | purge_cache is refused on a connection token with Read-only everywhere on, and for a Viewer sign-in |
| Confirmation | None on the Hub; your client's prompt is the gate |
Rules worth keeping
- Name the site. With several sites, an unclear name should make the agent ask, and the Hub tells it to.
- A purge of every site is one call with site: "all". The Hub tells the agent to confirm it with you once before it runs.
- Purge the narrowest type that fixes the problem, then warm the cache, so visitors do not all hit uncached pages at once.
- A fan-out result is reported per site. Treat some sites failing as a partial result, not a failure of the whole call.
Good to know with ChatGPT dots
A scheduled task is the risky place for a purge. Nobody is watching when it runs, and a custom rule set to Take action without asking would let a recurring prompt purge your sites unattended. Keep scheduled tasks to reads such as get_cache_status, and do purges in a conversation where you can answer the dot. The app signs in with OAuth and gets the scopes ChatGPT asks for, so the Hub's Read-only everywhere switch, which belongs to the connection token, does not apply here; a dot that should only report needs a sign-in as a Viewer member of the workspace, which refuses every purge. Pause in the dot's profile menu stops its work at once. Dots are also limited by plan: OpenAI lists Pro users outside the European Economic Area, Switzerland and the UK, Business Premium, and a beta on Enterprise, Edu and Healthcare that an admin turns on.
More prompts for this job
They work in any client connected to xSpeed Hub.
Use xSpeed Hub to purge the page cache on blog.
I just changed the theme CSS on shop. Use xSpeed Hub to purge only the assets cache there.
With xSpeed Hub, purge every site in my workspace and tell me which ones failed.
Use xSpeed Hub to purge shop, then purge its Cloudflare edge cache too.
With xSpeed Hub, purge the docs site and start the preloader so it is warm again.
Using xSpeed Hub, what purge type should I use after updating a plugin that changes the checkout page?
Frequently asked questions
Keep going
Purge the cache with other agents
More with ChatGPT dots
Documentation
- How to enable Page Cache
- How to warm your cache ahead of visitors
- Managing your fleet with xSpeed Hub
- How to write prompts for xSpeed Hub
- ChatGPT dots + xSpeed
- Every AI agent that works with xSpeed
From the blog