# Manage every WordPress site at once with GitHub Copilot in VS Code

> Managing every WordPress site at once with GitHub Copilot in VS Code means asking the chat for one xSpeed Hub action across your whole workspace and reading a result for each site next to your code.

Page: https://xspeedcache.com/agent/github-copilot/fleet/
Last updated: October 2026

You write the code for a group of WordPress sites in VS Code, and Copilot chat is the quickest place to say what should happen to them all once a change ships. You ask it to purge every site and warm them again. Copilot picks purge_cache, then start_preloader, and sends each with site set to "all" to the xSpeed Hub server you added to the editor. The two calls cover every site in the workspace you connected.

The Hub runs the sites in turn, one second apart, and returns one result per site with ok, plus data or an error. Copilot can print that as a short list in the chat. If one site is unreachable, that site is reported as failed and the others stay done, and the reply should say so instead of calling the whole run good or bad. Only seven tools take "all"; for anything else Copilot names a site and calls it again for the next one.

VS Code starts in Manual permissions, so a tool call that is not auto-approved shows a confirmation, and you can allow it once, for the session, for the workspace or for all future calls. Allow all, Autopilot and global auto-approval skip those prompts, external tool calls included. The Hub adds its own instruction to the agent to confirm once with the number of sites before a fleet-wide purge, toggle, settings change or preloader call. That second one is guidance to the model, not a lock, and it does not name optimize_site, so the dialog and the scope on your connection are the things to rely on.

## Set up GitHub Copilot in VS Code 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 to your user mcp.json

Open the Command Palette and run MCP: Open User Configuration, then add this entry. Servers in your user profile are available in every workspace. MCP: Add Server walks you through the same thing, and the project-level .mcp.json file works too if you want the entry shared with your team; that file uses a top-level mcpServers object instead of servers.

File: `mcp.json (MCP: Open User Configuration)`

```json
{
  "servers": {
    "xspeedhub": {
      "type": "http",
      "url": "https://app.xspeedcache.com/xspeed/mcp"
    }
  }
}
```

### 3. Start the server and sign in

Run MCP: List Servers, pick xspeedhub and choose Start. VS Code asks whether you trust the server, then opens a browser page where you sign in to xSpeed Hub and approve access. There is no token to paste, and VS Code keeps the credentials it receives. Open the Chat view and use the Configure Tools button to see the xSpeed tools.

```
MCP: List Servers
```

Full setup: https://xspeedcache.com/agent/github-copilot/

### 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 VS Code the default permission level is Manual permissions: a tool call that is not auto-approved shows a confirmation, and you can allow it once or for the session, the workspace or all future calls. Chat: Manage Tool Approval lists tools grouped by MCP server, so you can trust get_cache_status and the other reads while purge_cache and update_settings stay on a prompt. Allow all, Autopilot and global auto-approval skip those prompts, including for external tool calls, and then a write runs as soon as your connection allows writes. xSpeed Hub has no confirmation step of its own.

## Prompts

- Use xSpeed Hub to purge the cache on every WordPress site in my workspace, then start the preloader on all of them.
- With xSpeed Hub, benchmark all sites and show the cached and uncached response times in a table.
- Ask xSpeed Hub to stop the preloader on every site, then check which ones still report a running crawl.

## Example session

```
You: Use xSpeed Hub to stop the preloader everywhere, it is hammering the origins during the sale.
  → list_sites [read-only]: 10 sites in the workspace
Agent: This will touch all 10 sites by stopping the preloader on each. Proceed?
You: Yes.
  → stop_preloader(site: all) [changes site]: 9 stopped; 1 was already idle
  → get_preloader_status(site: shop) [read-only]: idle, last run finished
Agent: Nine preloaders stopped and one was already idle. I checked shop and it reports idle.
```

## How it works

1. **See what you can reach**: list_sites returns each site's handle, URL, status and scopes. When you have more than one workspace, list_workspaces returns each one's handle, id, your role, its site count, which one is the default, and whether this connection can reach it.
2. **Choose the scope of the call**: The agent passes site: "all" for every site in one workspace, or an array of handles for exactly those sites. For a workspace other than the default it also passes the workspace argument. Omit workspace and the call acts on the default workspace.
3. **Confirm once**: Before a purge, toggle, settings change or preloader call that touches every site, the Hub tells the agent to say "this will touch all N sites" and wait for you, then make one call. That instruction does not name optimize_site, so for it your client's prompt is the gate. It is guidance to the agent, not a lock. It is one tool call, so one approval in your client covers every site in it.
4. **Run it as one call**: The Hub runs the sites one after another with a one-second pause between live calls, so a fleet purge is not a burst of traffic at your servers. Revoked sites are skipped from "all". Each site's action lands in the activity log as its own row.
5. **Read the result per site**: The reply is a summary of targets, succeeded and failed, plus one row per site with ok and either its data or its error. Some sites failing is a partial success. Only a run where every site failed comes back as an error.
6. **Follow up on the failures**: The agent reports which sites failed and why, then retries just those handles with an array. Tools that read one site, such as get_cache_status and get_health, do not fan out, so a fleet-wide check means one call per site.

## Reference

| | |
| --- | --- |
| Fan-out tools | purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site, run_benchmark |
| Selector | site: "all", or an array of handles |
| What all covers | Every site this connection can see in one workspace, minus revoked ones |
| Pacing | One after another, with a 1 second pause between live calls |
| Result | summary (targets, succeeded, failed) and a row per site: ok, then data or error |
| Partial failure | Reported per site; the call counts as an error only when every site failed |
| Workspace argument | Optional. Omit it for the default workspace; name one by its handle or id from list_workspaces |
| Reach | Fixed when you approve the connection; list_workspaces shows reachable: false for the rest |
| Not fan-out | get_health, get_cache_status and every other tool take one site per call |
| Slow tools | optimize_site takes up to 2 minutes per site; a target_score run is capped at 12 rounds per call |
| Read-only | The connection token with Read-only everywhere on, or a Viewer sign-in, refuses every fan-out write; run_benchmark works. An OAuth sign-in gets the scopes the client asks for |
| Hub daily pass | Re-verifies sites, snapshots cache status and hit ratio, reads stored reports, alerts by Slack webhook or email |

## Rules

- Confirm once, then call once. The Hub has no confirmation step of its own, so your client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are the gates that matter. The Hub's "this will touch all N sites" is an instruction to the agent for purge, toggle, settings and preloader calls, and it does not name optimize_site.
- "all" is one workspace, never every workspace. To act in another workspace, name it. A write to a non-default workspace must name it, and an array of handles is looked up only in the workspace the call names.
- Read every result per site. Treat some sites failing as a partial result, and never accept a blanket "done" from the agent.
- Try a behaviour change on one site before you send it to the fleet. toggle_cache and update_settings on every site are one call, and each site checks values against its own settings, so a Pro setting can fail on a Free site.
- optimize_site on many sites is slow, because each site can take up to two minutes inside one call. Use dry_run first, or name a short list of handles.
- The Hub has no scheduler for agent prompts. Its own daily pass and alerts run without an agent, and an agent can only act when you send a prompt or your AI client runs one on a timer.

## Good to know with GitHub Copilot in VS Code

When the VS Code dialog offers to allow a tool for the session or the workspace, think about which tool you are clicking it for. Allowing purge_cache or start_preloader for the workspace also allows the all-sites form of the call, because the dialog is about the tool and not the site argument. Chat: Manage Tool Approval lists tools grouped by MCP server, so trust the reads there and leave the fan-out tools that write on a prompt. Also mind the tool budget: a chat request can enable at most 128 tools, and the 29 xSpeed Hub tools count toward that alongside every other MCP server you have enabled.

## More prompts for this job

They work in any client connected to xSpeed Hub.

- Use xSpeed Hub to list every site I can reach, and every workspace, and say which workspace you act in by default.
- With xSpeed Hub, purge the cache on every site in my workspace and tell me which ones failed.
- Use xSpeed Hub to run a benchmark on all my sites and rank them by cached response time.
- Use xSpeed Hub to start the preloader on blog, shop and docs only.
- With xSpeed Hub, turn page caching on for every site where it is off. Check each site first.
- Use xSpeed Hub to stop the preloader everywhere. The servers are busy.
- Ask xSpeed Hub to preview a safe optimize_site pass on every site with dry_run and summarize what it would change.
- Use xSpeed Hub to purge every site in the client-acme workspace, not my default one.

## Frequently asked questions

### Can Copilot chat run xSpeed on all sites from VS Code?

Yes. After you add the Hub as an MCP server and sign in, ask for a purge, a preload or a benchmark on all sites. Copilot sends a single fan-out call and the Hub returns one result per site.

### What does the allow for this workspace choice do?

It lets that tool run without asking again in the workspace. For xSpeed that includes calls with site set to all, so allow only the read tools that way and keep the fan-out write tools on the dialog.

### What does site "all" cover?

Every site the connection can see in one workspace. It never crosses workspaces, and revoked sites are skipped. If your connection is limited to some sites, "all" quietly means the sites you are allowed, with no error naming the rest. To act in another workspace, the agent names it with the workspace argument.

### What happens if one site fails?

The other sites still run. The reply has a summary and a row for each site with ok and its data or its error, so a site that was unreachable is named. A run counts as an error only when every site failed. Ask the agent to retry just the failed handles.

### Can the agent check the health of every site in one call?

No. get_health and get_cache_status take one site per call, so the agent loops. The tools that fan out are purge_cache, toggle_cache, update_settings, start_preloader, stop_preloader, optimize_site and run_benchmark. The Hub dashboard has a fleet overview for health.

### Does the Hub watch my fleet when no agent is running?

Yes, on its own. A daily pass re-verifies each site, retrying a failed probe once, snapshots cache status and hit ratio, and reads the PageSpeed and GTmetrix reports your sites already stored. It can alert you by Slack webhook or email when a site becomes unreachable, caching is switched off, the hit ratio falls below a floor you set, or a score regresses. Each alert fires once per incident, not every day.

### Does the Hub ask before it touches every site?

The Hub has no confirmation step. Its instructions tell the agent to confirm once with you, saying how many sites a call will touch, but that is guidance and not a lock. Your AI client's approval prompt and a read-only connection (the connection token with Read-only everywhere on, or a Viewer sign-in) are what stop a write. The instruction covers purge, toggle, settings and preloader calls, not optimize_site. The dashboard's own Purge all button does confirm before it runs.

### Can the agent add sites, remove sites or change who has access?

No. It cannot add, remove or rename sites, change members, roles or billing, mint or rotate tokens, or widen the workspaces this connection reaches. Those stay in the Hub dashboard.

## Manage every site at once with other agents

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

## More with GitHub Copilot in VS Code

- [Purge the WordPress cache with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/purge-cache/)
- [Find out why WordPress pages are not cached with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/troubleshoot-cache/)
- [Scan a website for speed problems with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/speed-scan/)
- [Run and track PageSpeed tests with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/optimize-site/)
- [Tune WordPress cache settings with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/cache-settings/)
- [Warm the WordPress cache with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/preload-cache/)
- [Set up the Redis object cache with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/object-cache/)
- [Manage Cloudflare caching with GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/cloudflare/)

## Documentation

- Managing your fleet with xSpeed Hub: https://xspeedcache.com/docs/managing-your-fleet-with-xspeed-hub/
- Teams, roles and workspaces in xSpeed Hub: https://xspeedcache.com/docs/hub-teams-and-workspaces/
- Scoped AI connections in xSpeed Hub: https://xspeedcache.com/docs/hub-connection-scopes/
- Connecting to xSpeed Hub: https://xspeedcache.com/docs/connecting-to-xspeed-hub/