# Warm the WordPress cache with Muse

> Warming the WordPress cache with Muse means messaging Meta's personal agent to start the xSpeed preloader on a site through its xSpeed Hub custom connector, then asking it later how much of the site is warm.

Page: https://xspeedcache.com/agent/muse/preload-cache/
Last updated: October 2026

Muse is the one you message from your phone, and warming fits that well: one message to start, one message later to check. You are away from your desk after a purge on blog and you write in WhatsApp: warm blog and tell me when it is mostly done. Muse calls start_preloader, the plugin queues the sitemap, and Muse replies with how many URLs were queued. Later you ask again and it reads get_preloader_status for the processed count and any errors.

Whether the start works depends on the token behind the connector. Muse keeps the Hub's connection token in its Secure Credentials Store, and if Read-only everywhere is on, as it is for many people on a first try, the Hub refuses start_preloader and stop_preloader. get_preloader_status keeps working, so a read-only Muse can still watch a crawl that the plugin's own schedule started. To let Muse start crawls, the workspace owner turns the switch off on the Connect AI page. If the module is off on a site, the default on a fresh install, Muse can propose turning it on with update_settings.

Meta says Muse will not take many important actions without your approval by default, that many connectors can be set to retrieve data only, and that you change when it asks in Settings. Its Sentinel agent also asks you for permission when something needs to leave Muse's secure machine. xSpeed Hub has no confirmation step of its own, and it treats the preloader as low-risk, asking the agent to confirm only when the site is unclear or the call covers every site. So for a single named site, Muse's own approval settings and the token decide whether a start runs.

## Set up Muse 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. Copy the connection token from xSpeed Hub

Sign in at app.xspeedcache.com as the workspace owner and open Connect AI. Copy the connection token. For a first try, turn on Read-only everywhere: the Hub then refuses every write tool on that token, so Muse can read but not purge or change settings.

```
xSpeed Hub  >  Connect AI  >  connection token (Read-only everywhere: on)
```

### 3. Ask Muse to create a custom connector

Send this message to Muse in the app, on muse.ai or in WhatsApp, and follow the steps Muse gives you. When it asks for the credential, give it the token as a Bearer token. Meta does not review custom connectors, so only finish this for the request you started yourself.

```
Create a custom connector called xSpeed Hub for the MCP server at
https://app.xspeedcache.com/xspeed/mcp
It authenticates with a Bearer token in the Authorization header. Once it is connected, use xSpeed Hub to list my sites.
```

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

### 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. Meta says Muse will not take many important actions without your approval by default, that many connectors can be set up to only retrieve data, and that you change when Muse asks for approval in its Settings. Muse's separate Sentinel agent also decides what leaves its secure machine and asks you for permission when needed. xSpeed Hub has no confirmation step of its own, so a write runs as soon as Muse calls it and your connection allows writes. The firm stop here is the token: with Read-only everywhere on, the Hub refuses every write tool, whatever Muse decides. Turn it off only when you want Muse to purge or change settings, and read each question Muse asks before you answer yes.

## Prompts

- Use xSpeed Hub to start the preloader on blog and tell me how many URLs it queued.
- Using xSpeed Hub, how far through its crawl is shop? Give me processed against total and any errors.
- With xSpeed Hub, read the preloader settings on docs and tell me what schedule it runs on. Do not change anything.

## Example session

```
You: Use xSpeed Hub to warm blog. I purged it an hour ago.
  → start_preloader(site: blog) [changes site]: This connection is read-only; write tools are not permitted.
Agent: The Hub refused the start because your connection token has Read-only everywhere on, so I can watch a crawl but not start one. Want me to read the preloader status instead?
You: Yes, read it.
  → get_preloader_status(site: blog) [read-only]: idle, last run 6 hours ago, 210 of 210 URLs processed
Agent: The last crawl on blog finished six hours ago, before your purge, so the pages it warmed were cleared. Turn Read-only everywhere off in the Hub if you want me to start a new crawl, or let the plugin's own schedule run.
```

## How it works

1. **Check the cache and the preloader**: get_cache_status tells the agent whether page caching is on, because there is nothing to fill when it is off. get_preloader_status shows whether a crawl is already running, so the agent does not start a second one.
2. **Make sure the preloader is switched on**: The preloader module is off on a fresh install, and the site refuses start_preloader until it is on. The agent can read the module with get_settings and, if you agree, switch it on with update_settings on the preloader module. The Hub tells the agent to briefly confirm intent before an update_settings call, but that is guidance to the agent, not a lock.
3. **Start the crawl**: start_preloader makes the site read its sitemap, follow any nested sitemap indexes, drop URLs that your cache exclusion rules skip, and queue the rest. The call returns once the queue is built; the pages are then fetched in the background, a few per run. For every site at once the agent passes site: "all", and the Hub starts the sites one after another with a one-second pause.
4. **Watch the progress**: get_preloader_status reports whether a crawl is running, how many URLs it has processed out of the total, the last URL it visited and the most recent errors. It works on one site at a time, so for several sites the agent calls it once per site.
5. **Read what failed**: A page that answers 403 or 406 usually means a server firewall is blocking the warmer by its user-agent, not that the page is broken. The status message names the user-agent to allow. A crawl that queues no URLs is reported as an error with the reason, not as a success.
6. **Stop it if the server struggles**: stop_preloader ends a running crawl. It is safe mid-run: pages already warmed stay cached. The agent can stop one site or every site in the workspace.

## Reference

| | |
| --- | --- |
| Start and stop | start_preloader and stop_preloader (write) |
| Progress | get_preloader_status (read): running or not, processed out of total, last URL, recent errors |
| What gets crawled | The sitemap (the WordPress one at /wp-sitemap.xml unless you set another), nested indexes followed, excluded URLs skipped |
| Needs | The preloader module switched on (it is off by default) and page caching on |
| Pages per run | 5 by default, 1 to 50, set in the preloader module |
| Schedule setting | manual, hourly, daily or weekly, set in the preloader module |
| Every site at once | start_preloader and stop_preloader accept site: "all"; get_preloader_status does not |
| Fan-out pacing | Sites start one after another with a 1 second pause, one result per site |
| Warmer user-agent | xSpeed-Warmer/1.0, the string a firewall rule would need to allow |
| Stopping | Safe mid-run; warmed pages stay cached |
| Read-only access | A Viewer member's sign-in, or the connection token with Read-only everywhere on: start_preloader and stop_preloader are refused; get_preloader_status works. An OAuth sign-in by anyone else gets the scopes the client asks for. |
| Confirmation | None on the Hub; your client's prompt is the gate |

## Rules

- Warm after a purge, not instead of one. The Hub tells the agent that starting the preloader after a purge saves the next visitor from paying for the rebuild.
- A crawl requests every page in the sitemap, so it adds load to the origin. Start with one site, and on a small host keep Pages per run low or stop the crawl if the site slows.
- start_preloader and stop_preloader are write tools. The Hub calls the preloader low-risk and only asks the agent to confirm when the target site is unclear or the call covers every site, so your client's approval prompt and read-only access (a Viewer sign-in, or the connection token with Read-only everywhere on) are the gates that matter.
- A fan-out only starts the crawls. Check each site with get_preloader_status afterwards, and treat some sites failing to start as a partial result, not a failure of the whole call.

## Good to know with Muse

Meta's pages describe no scheduled tasks for Muse, so it warms when you message it. For a crawl that repeats, set the plugin's own Schedule in the preloader module, which runs hourly, daily or weekly inside WordPress, and use Muse to check on it. That split also lets you keep the token read-only: the schedule warms the site, and Muse only reads get_preloader_status. If you do turn Read-only everywhere off for Muse, remember that it opens every write tool on that token, purges and settings changes included, for every client that sends it. Meta does not review custom connectors, and Muse is rolling out in the US first.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Use xSpeed Hub to start the preloader on shop and tell me how many URLs it queued.
- Using xSpeed Hub, how far through its crawl is blog? Show processed against total and any errors.
- With xSpeed Hub, purge the cache on docs, then warm it again.
- Use xSpeed Hub to start the preloader on every site in my workspace and tell me which ones refused.
- Use xSpeed Hub to stop the preloader on shop. It is slowing the server down.
- The preloader on shop says it is disabled. Use xSpeed Hub to turn the module on, then start the crawl.
- Using xSpeed Hub, which of my sites has no running crawl and a low hit ratio?

## Frequently asked questions

### Why can Muse read the preloader but not start it?

The connection token is probably set to Read-only everywhere, and the Hub then refuses start_preloader and stop_preloader while get_preloader_status keeps working. The workspace owner can turn that switch off on the Connect AI page in xSpeed Hub.

### Can Muse warm my site on a schedule?

Meta's pages describe no scheduled tasks for Muse. The preloader module in WordPress has its own Schedule setting, manual, hourly, daily or weekly, and Muse can check on those crawls when you ask.

### Why does start_preloader say the preloader is disabled?

The preloader module is off by default on a new install, and the site refuses to start a crawl until it is on. The agent can switch it on with update_settings on the preloader module, or you can turn it on in the xSpeed Cache panel in wp-admin. Page caching also has to be on, because the crawl exists to fill that cache.

### What does the preloader actually warm?

It reads the site's sitemap, which is the WordPress one at /wp-sitemap.xml unless you set a different sitemap URL, follows nested sitemap indexes and skips any URL your cache exclusion rules leave out. If the sitemap cannot be read, the site falls back to a list built from its own content and says so. If nothing at all is queued, the call reports an error with the reason.

### Can I warm every site with one prompt?

Yes. The agent passes site: "all" to start_preloader and the Hub starts the crawl on every site in the workspace one after another, returning a result per site. The Hub tells the agent to confirm that with you once first. The call only starts the crawls, so progress is read afterwards with get_preloader_status, one site at a time.

### Will warming slow my site down?

A crawl fetches your own pages, a few per run, so it adds load while it runs. The Pages per run setting controls how many, from 1 to 50 with a default of 5. If a site struggles, stop_preloader ends the crawl and the pages already warmed stay cached.

### Why do some pages fail with HTTP 403 or 406?

Those codes are what bad-bot firewall rules usually answer with, and they mean the warmer was judged by its user-agent, not that the page is missing. The warmer identifies itself as xSpeed-Warmer/1.0. Allow that user-agent in the server rule, or change it with the xspeed_preloader_user_agent filter, and run the crawl again.

### Can the agent keep my cache warm on a schedule?

The preloader has its own Schedule setting in WordPress: manual, hourly, daily or weekly. An agent can change it with update_settings. The Hub itself has no scheduler for agent prompts, so a prompt only runs when you send it or when your AI client runs it on a timer.

## Warm the cache with other agents

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

## More with Muse

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

## Documentation

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