# Purge the WordPress cache with Windsurf

> Purging the WordPress cache with Windsurf, which now ships as Devin Desktop, means asking its Devin Local agent, in the editor where you just edited the site, to clear the xSpeed cache and warm it again through xSpeed Hub.

Page: https://xspeedcache.com/agent/windsurf/purge-cache/
Last updated: October 2026

You are in Windsurf, now shipped as Devin Desktop, with a WordPress project open and the Devin Local agent in a tab. You edit a template, save, and want to see the change on the live site, so you tell the agent: purge the cache on shop. It calls list_sites to match the name, chooses a purge type from what you changed, and runs purge_cache. The call and its result appear in the agent thread.

The flow is quick because the agent sits next to your files. It can read what you touched, so for a stylesheet edit it can reason that assets is enough, and for a template edit that page is. What comes back is the plugin's report: the purge type, the site, how many entries cleared, and for all the object cache and a connected Cloudflare edge as well. Ask the agent to start the preloader and it queues the warm-up, then you can ask for the hit ratio a few minutes later.

Devin Local prompts before it calls any MCP tool, and in the prompt you can allow that one tool or the whole xspeedhub server, for this session or permanently. Smart mode lets a fast model run what it judges safe, and Bypass mode approves everything. xSpeed Hub has no confirmation of its own, so those settings and your connection scope are the gates. For a purge across every site the Hub also tells the agent to say that it will touch all the sites and wait for your yes.

## Set up Windsurf once

### 1. Put 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.

### 2. Add xSpeed Hub for the Devin Local agent

Run this in a terminal. Devin Local shares its MCP configuration with Devin CLI, and -s user saves the server to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows) so it applies to every project. Without -s, the command saves to local scope, which is the current project only.

```bash
devin mcp add -s user xspeedhub https://app.xspeedcache.com/xspeed/mcp
```

### 3. Sign in

Run the login command and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste, and the client keeps the credentials it receives. If the server later shows Needs auth in the Devin Local MCP list, click Authenticate, or run devin mcp logout and then login again.

```bash
devin mcp login xspeedhub
```

Full setup: https://xspeedcache.com/agent/windsurf/

### 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. The Devin Local agent prompts for approval before it calls any MCP tool. In the prompt you can allow that one tool or every tool on the xspeedhub server, for this session or permanently, and permission rules such as mcp__xspeedhub__get_cache_status allow, deny or always ask for a named tool. Smart mode lets a fast model run what it judges safe without a prompt, and Bypass mode approves everything, so with either of those a write reaches the Hub as soon as your connection allows writes. xSpeed Hub has no confirmation step of its own.

## Prompts

- I edited the product template on shop. Use xSpeed Hub to purge the page cache there and tell me how many pages were cleared.
- With xSpeed Hub, purge shop fully, start the preloader, and read the cache status when it finishes.
- Ask xSpeed Hub to purge every site in my workspace and list any that failed.

## Example session

```
You: Saved the new product template on shop. Use xSpeed Hub to make it show on the live site.
  → list_sites [read-only]: 6 sites; shop is shop.example.com
  → get_cache_status(site: shop) [read-only]: page cache on, 264 cached pages, hit ratio 71% in the last 24h
Agent: A template is HTML, so I will purge the page cache on shop and leave assets alone. Purge it?
You: Yes.
  → purge_cache(site: shop, type: page) [changes site]: 264 cached pages cleared
Agent: Cleared. Load the product page once and it rebuilds fresh. Want the preloader started?
```

## How it works

1. **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.
2. **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.
3. **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.
4. **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.
5. **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

- 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 Windsurf

Allowing the whole xspeedhub server in the prompt, or running Smart or Bypass mode, lets purge_cache run the moment the agent calls it. Allow single reads such as get_cache_status, add a rule that asks for mcp__xspeedhub__purge_cache, and approve writes one at a time. If you use the legacy Cascade agent instead, it can load at most 100 MCP tools across every server you have enabled, and the Hub's 29 count toward that, so turn other servers off if it cannot see purge_cache.

## 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

### Can Windsurf purge my WordPress cache?

Yes. Add xSpeed Hub as an MCP server and ask the Devin Local agent to purge the site you edited. It calls purge_cache with a type that fits and shows the result in the thread.

### Which Windsurf agent does this cover, and does it ask before a purge?

Windsurf now ships as Devin Desktop, and its primary agent is Devin Local. It prompts before it calls any MCP tool and lets you allow one tool or the whole server, while Smart and Bypass modes skip the prompt. The older Cascade agent stays for existing conversations and loads at most 100 MCP tools across all servers, of which the Hub takes 29.

### What is the difference between the purge types?

all clears every cache xSpeed manages for the site, including a connected Cloudflare zone or CDN. page clears the stored HTML pages, assets clears minified and combined CSS and JavaScript, object clears the Redis or Memcached object cache, and rest clears cached REST API responses.

### Does purging xSpeed also clear Cloudflare?

A purge of type all does, when the site has Cloudflare connected in xSpeed: it clears the page cache, the object cache and the Cloudflare edge, and reports each one. A page, assets or rest purge stays on your server. purge_cloudflare clears only the edge.

### Can I purge all of my sites with one prompt?

Yes. The agent passes site: "all" to purge_cache and the Hub purges every site in the workspace one after another, returning a result per site. The Hub tells the agent to confirm a write across every site with you once before it runs it.

### Will a purge slow my site down?

The next request to each purged page builds it fresh, which is slower than a cached hit. Starting the preloader right after the purge rebuilds the cache in the background so visitors mostly land on warm pages.

## Purge the cache with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/purge-cache/) · [Claude](https://xspeedcache.com/agent/claude/purge-cache/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/purge-cache/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/purge-cache/) · [Codex](https://xspeedcache.com/agent/codex/purge-cache/) · [Cursor](https://xspeedcache.com/agent/cursor/purge-cache/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/purge-cache/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/purge-cache/) · [Antigravity](https://xspeedcache.com/agent/antigravity/purge-cache/) · [Zed](https://xspeedcache.com/agent/zed/purge-cache/) · [Kiro](https://xspeedcache.com/agent/kiro/purge-cache/) · [OpenCode](https://xspeedcache.com/agent/opencode/purge-cache/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/purge-cache/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/purge-cache/) · [Grok Build](https://xspeedcache.com/agent/grok-build/purge-cache/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/purge-cache/) · [Grok](https://xspeedcache.com/agent/grok/purge-cache/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/) · [Muse](https://xspeedcache.com/agent/muse/purge-cache/) · [Manus](https://xspeedcache.com/agent/manus/purge-cache/) · [Kimi Code](https://xspeedcache.com/agent/kimi/purge-cache/) · [Paperclip](https://xspeedcache.com/agent/paperclip/purge-cache/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/purge-cache/)

## More with Windsurf

- [Find out why WordPress pages are not cached with Windsurf](https://xspeedcache.com/agent/windsurf/troubleshoot-cache/)
- [Scan a website for speed problems with Windsurf](https://xspeedcache.com/agent/windsurf/speed-scan/)
- [Run and track PageSpeed tests with Windsurf](https://xspeedcache.com/agent/windsurf/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Windsurf](https://xspeedcache.com/agent/windsurf/optimize-site/)
- [Tune WordPress cache settings with Windsurf](https://xspeedcache.com/agent/windsurf/cache-settings/)
- [Warm the WordPress cache with Windsurf](https://xspeedcache.com/agent/windsurf/preload-cache/)
- [Set up the Redis object cache with Windsurf](https://xspeedcache.com/agent/windsurf/object-cache/)
- [Manage Cloudflare caching with Windsurf](https://xspeedcache.com/agent/windsurf/cloudflare/)
- [Manage every WordPress site at once with Windsurf](https://xspeedcache.com/agent/windsurf/fleet/)

## Documentation

- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/
- How to warm your cache ahead of visitors: https://xspeedcache.com/docs/preloader/
- Managing your fleet with xSpeed Hub: https://xspeedcache.com/docs/managing-your-fleet-with-xspeed-hub/