How NanoClaw handles this
NanoClaw's weekday report lands in Telegram at eight, posted by a scheduled task you created with ncl tasks create, and one line stands out: docs has zero cached pages. You reply in the chat with the trigger word, @Andy by default, and ask the agent to use xSpeed Hub to find out which sites are not serving from cache and why. The agent runs in its own container on your machine, with xSpeed Hub added to its agent group as a remote MCP server.
The quickest first step is run_benchmark for every site in one call, which times each home page cached and uncached and returns a result per site. docs is the only one where the cached request was not a hit. get_cache_status shows caching on with nothing saved, and get_health names the cause: the cache directory is not writable, so nothing can be cached whatever the switches say. That often follows a restore or a migration that left files owned by another user. The agent cannot change folder permissions through the Hub, so it tells you what to fix on the server and offers to benchmark docs again when you reply.
Every tool in this diagnosis only reads, so it works on a connection token with Read-only everywhere on, which is the setting the scheduled report should use anyway. NanoClaw's documentation gates adding a server behind approval but describes no per-tool prompt for tool calls, so whether the agent asks before a tool runs depends on your fork. With the switch on, the Hub refuses every write tool whatever the agent decides, which makes a diagnosis safe to run from a phone.
Set up NanoClaw once
Already connected? Skip to the prompts. Alternatives and troubleshooting are on the NanoClaw 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.
2Add xSpeed Hub to your agent group
Copy the connection token from Connect AI in the Hub (only the workspace owner sees it). Then run this on the machine that hosts NanoClaw, with your agent group's ID from ncl groups list. The header goes in as a JSON object, because NanoClaw refuses credentials inside the URL. NanoClaw may ask an admin to approve the change.
ncl groups config add-mcp-server --id <group-id> --name xspeedhub \
--url https://app.xspeedcache.com/xspeed/mcp \
--headers '{"Authorization":"Bearer <your connection token>"}' 3Restart the group and ask
The new server takes effect after a restart. Then message your agent with its trigger word, @Andy by default, and ask something that names xSpeed Hub.
ncl groups restart --id <group-id>
Full NanoClaw 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. Whether NanoClaw asks you before an MCP tool runs depends on how your fork and its admins are set up; its documentation gates adding a server behind approval but describes no per-tool prompt for calls. xSpeed Hub has no confirmation step of its own, so a write runs as soon as the agent calls it and your connection allows writes. The Hub tells the agent to confirm the target site and to ask once before a write that touches every site, which in NanoClaw shows up as a question in the chat. The firm stop is the token: with Read-only everywhere on, the Hub refuses every write tool. Keep it on for scheduled tasks.
What do I ask?
Three prompts written for NanoClaw. More for this job are below.
@Andy use xSpeed Hub to benchmark every site and name any where the cached request was not a hit.
@Andy with xSpeed Hub, read the health report for docs and quote any warning. Change nothing.
@Andy using xSpeed Hub, check docs again now that the folder permissions are fixed.
What happens, step by step
When a WordPress page is not served from cache, the cause is usually one of a few things: caching is off, the cache drop-in or the WP_CACHE constant is missing, another caching plugin is in the way, or the pages carry something that makes them uncacheable. Through xSpeed Hub an agent can read the cache status, run the site's full health diagnostics, time a cached request against an uncached one, and check which Pro features would help, all without changing anything.
01
Start with the quick summary
get_cache_status returns whether page caching is on, the stats (cached pages, size, hit ratio, last purge) and the web server xSpeed detected. It is a glance. If caching is off, or the hit ratio is far below what you expect, the agent moves on to the diagnostic.
02
Run the diagnostic
get_health is the tool for troubleshooting. It returns the environment checks with pass or warn tones (the advanced-cache.php drop-in, the WP_CACHE constant, rewrite rules, PHP and WordPress versions, caching plugin conflicts), the cache stats, 24 hourly hit and miss buckets and a 30-day hit-ratio series. The Hub tells the agent to use it, not get_cache_status, when you are troubleshooting rather than glancing.
03
Time cached against uncached
run_benchmark requests the home page once with the cache bypassed and once normally, after a warm-up request, and returns the timings. If the second request still is not a cache hit, the page cache is not serving the home page, and the result says so. It measures xSpeed's own response time. It does not return a Lighthouse score.
04
Read what the checks mean
A warn is a lead, not always a fault. A static-file rewrite warning, for example, can mean the nginx snippet is not in your server config yet, or that xSpeed could not verify it, which is not evidence the config is wrong. The agent reads the detail line and tells you which one it is.
05
Fix it or hand it over
If caching is simply off, toggle_cache turns it on. If another caching plugin owns the drop-in, the site refuses to enable xSpeed and says why; removing the other plugin is yours to do. If nothing explains it, contact_support emails xSpeed support with the agent's summary, after the agent has confirmed the message with you.
Reference
| Quick check | get_cache_status (read): cache on or off, stats, detected web server |
|---|---|
| Diagnostic | get_health (read): environment checks, 24 hourly buckets, 30-day hit-ratio series, recent activity |
| One site per call | get_health does not accept site: "all"; call it for each site you care about |
| Benchmark | run_benchmark (read): home page only, cache bypassed against cache served, timings in milliseconds |
| Benchmark on every site | run_benchmark accepts site: "all" or a list of handles, one result per site |
| Benchmark history | get_benchmark_history reads past runs and the settings changes on the same timeline |
| Pro suggestions | get_pro_audit (read): which Pro features would help this site, from its settings and stats |
| Hit ratio scope | Counts requests that reach your server; pages answered by a CDN or Cloudflare edge are not counted |
| Support | contact_support emails xSpeed support with your account email and site list attached; classed read |
| Turning caching on | toggle_cache (write); refused by the site when another plugin owns the cache drop-in |
Rules worth keeping
- Diagnose with the read tools first. get_cache_status, get_health, run_benchmark and get_pro_audit change nothing on the site, so a read-only connection can run all of them. For clients that send the connection token, that means Read-only everywhere on; an OAuth sign-in gets the scopes the client asks for, unless the member is a Viewer.
- Do not answer a PageSpeed question with run_benchmark. It measures cached against uncached response time and returns no Lighthouse score; for a score, use the speed test or scan jobs.
- toggle_cache is a write. It runs as soon as your connection allows writes, and the Hub tells the agent to confirm the target site first. That is guidance to the agent, so your client's approval prompt is the gate that matters.
- contact_support sends a real email. The Hub tells the agent to confirm the message with you before sending, but the tool is classed read, so even a read-only connection can send one.
- The agent cannot edit your server configuration or another plugin's settings. When a check needs an nginx snippet or a conflicting plugin removed, it tells you what to do and you do it.
Good to know with NanoClaw
One gap remains on a read-only token. contact_support is classed as a read by the Hub, so the agent can still email xSpeed support with your account email and site list, and the Hub's request that the agent confirm the message with you first is guidance to the model, not a lock. Say in the scheduled task's prompt that it must not contact support, and name the chat that gets the report, since a scheduled task has no chat attached. The token itself lives in the agent group's container configuration on your host, so keep that machine and its backups private, or hold the token in NanoClaw's credential gateway. The server belongs to one agent group, so add it to each group that should reach your sites and restart that group.
More prompts for this job
They work in any client connected to xSpeed Hub.
Using xSpeed Hub, why is the cache hit ratio so low on shop? Run the full health check and tell me the most likely cause.
Using xSpeed Hub, is page caching actually working on blog? Benchmark cached against uncached and tell me if the second request was a hit.
xSpeed Hub's get_health on docs shows a warning about the static-file rewrite. What does it mean and do I need to act?
Use xSpeed Hub to check whether another caching plugin is conflicting with xSpeed on shop.
Caching looks off on the staging site. Use xSpeed Hub to turn it on and tell me if the site refuses.
Using xSpeed Hub, which Pro features would help the shop site, based on how it is set up now?
With xSpeed Hub, compare the last few benchmark runs on blog and tell me whether my settings changes helped.
Frequently asked questions
Keep going
Find out why pages are not cached with other agents
More with NanoClaw
Documentation
- How to read your cache diagnostics
- Understanding cache hits and misses
- How to check your site health
- Common problems and troubleshooting
- How to enable Page Cache
- How to write prompts for xSpeed Hub
- NanoClaw + xSpeed
- Every AI agent that works with xSpeed
From the blog