# Set up the Redis object cache with Muse

> Setting up a Redis object cache with Muse means messaging Meta's personal AI agent to check, test and enable Redis on a WordPress site through xSpeed Hub, from the Muse app, muse.ai or WhatsApp.

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

You are away from your desk and a customer says checkout on shop felt slow this morning. You message Muse in WhatsApp, ask whether the object cache is working, and add that nothing should change. Muse calls get_object_cache_status through the xSpeed Hub connector, which reports whether the object-cache.php drop-in is installed, which backend is configured and whether the connection is degraded, then test_object_cache, which makes the site connect to Redis and write and read a probe value.

What comes back fits a phone screen: the drop-in is installed, but Redis refuses the connection, so the site has fallen back to WordPress's own cache. It still works, yet each request can wait up to the one second connection timeout. A refused connection usually means the Redis service stopped, which is a hosting task, so the useful next step is a message to your host, not a toggle. When the host has restarted it, ask Muse to run the test again. If you are setting Redis up for the first time instead, the order is the same: status, then test, and toggle_object_cache with enabled set to true only after a pass.

What differs in Muse is where the stop sits. Meta says Muse will not take many important actions without your approval by default, that you change when it asks in Settings, and that its Sentinel agent decides what leaves its secure machine. xSpeed Hub has no confirmation step of its own. The firm stop is the connection token Muse keeps in its Secure Credentials Store: with Read-only everywhere on, the status and the test still work and the Hub refuses toggle_object_cache and flush_object_cache. That suits checks from a phone.

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

- With xSpeed Hub, is the object cache working on shop? Test Redis and do not change anything.
- Use xSpeed Hub to test Redis on shop again; my host says they restarted it.
- Ask xSpeed Hub for the object cache status on blog, in two short lines.

## Example session

```
You: With xSpeed Hub, is the object cache working on shop? Do not change anything.
  → get_object_cache_status(site: shop) [read-only]: Drop-in installed. Backend: Redis, degraded.
  → test_object_cache(site: shop) [read-only]: Failed. Connection refused on 127.0.0.1:6379.
Agent: The drop-in is in place, but Redis refuses the connection, so shop has fallen back to WordPress's own cache. It works, but each request can wait up to the one second timeout. Connection refused usually means the Redis service stopped. Ask your host to restart it, then tell me.
You: Host restarted it. Test again.
  → test_object_cache(site: shop) [read-only]: Connected. Probe value written and read back.
Agent: Redis answers again, so shop is back on the object cache. Nothing was changed on the site.
```

## How it works

1. **Read the current state**: get_object_cache_status reports whether the object-cache.php drop-in is installed, which backend is configured, Redis or Memcached, and its stats. It does not prove the server answers, so a clean status is not a green light.
2. **Test the connection first**: test_object_cache opens a live connection to the configured server and does a read and write probe with the settings saved on the site. A failure comes back with the server's own reason, such as a wrong password, a refused connection or a permission error. The Hub tells the agent to run this before toggle_object_cache.
3. **Fix the connection if the test fails**: get_settings reads the object-cache module, with secrets masked. update_settings changes it, for example the host or port. On a managed host that defines these values in wp-config.php, the fields are read-only and a write that tries to change one is refused with the name of the constant. For a host that wants the constants pasted, get_object_cache_status with detail set to snippet returns the wp-config.php block.
4. **Turn it on**: toggle_object_cache with enabled true makes the site test the connection again, write the connection constants into wp-config.php and install the object-cache.php drop-in. If the test fails, it stops with "Could not enable" and writes nothing. If wp-config.php is not writable, the drop-in goes in and the reply tells you to add the snippet by hand. The Hub tells the agent to briefly confirm intent first.
5. **Check it took**: The drop-in loads on the next request, so the agent reads get_object_cache_status again after a page load and runs test_object_cache once more. The status also warns when the cache connects but refuses writes, so a connected cache that stores nothing does not pass as healthy.
6. **Flush when stale data survives**: flush_object_cache empties the persistent object cache. Use it when old options, transients or query results outlive a page cache purge. It does not touch the page cache; purge_cache does that.

## Reference

| | |
| --- | --- |
| Read tools | get_object_cache_status and test_object_cache, both work on a read-only connection |
| Write tools | toggle_object_cache (enabled true or false) and flush_object_cache |
| Backends | Redis or Memcached |
| Status detail | status (default) or snippet, the wp-config.php constants block |
| What status proves | Drop-in installed, backend configured, stats. Not that the server is reachable |
| What the test proves | A live connect and a read and write probe on the saved settings, with the server's own error on failure |
| Enable does | Tests the connection, writes connection constants to wp-config.php, installs the object-cache.php drop-in |
| Disable does | Removes xSpeed's drop-in and its wp-config.php block; a drop-in owned by another plugin is left alone |
| Connection timeout | 1 second by default, set in the object-cache module |
| Settings module | object-cache, for get_settings and update_settings |
| Every site at once | None of these tools accept site: "all"; one site per call |
| Confirmation | None on the Hub; your client's prompt is the gate |

## Rules

- Test before you toggle. The Hub tells the agent to run test_object_cache first, because a cache server that does not answer slows every request while the page cache still looks healthy.
- Keep the Redis password out of the chat. get_settings masks it, but the wp-config.php snippet is built from the saved settings and can include a saved password. Set secrets in wp-config.php or in the xSpeed panel.
- toggle_object_cache and flush_object_cache are write tools. The Hub tells the agent to briefly confirm intent for the object-cache toggles, but that is guidance, not a lock. Your client's approval prompt and a read-only grant are the gates that matter. A read-only grant means the connection token with Read-only everywhere on, or a Viewer member's sign-in; an OAuth sign-in gets the scopes the client asks for, which are read and write by default.
- If another plugin owns the object-cache.php drop-in, turn its object cache off in that plugin. xSpeed leaves a drop-in it did not install in place when you disable.
- A flush clears cached data, so the next requests rebuild it from the database and the site is briefly slower. Flush one site, then check it, before you repeat it.

## Good to know with Muse

Do not ask Muse for the wp-config.php snippet. It is built from the saved settings and can contain the Redis password, and Meta notes that what Muse has used may stay in its memories and your conversation history even after you disconnect the connector. Turn Read-only everywhere off only when you want Muse to enable or flush, and back on afterwards, because the token serves 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.

- Using xSpeed Hub, is a persistent object cache running on shop, and which backend does it use?
- Use xSpeed Hub to test whether Redis is reachable from shop. Do not change anything.
- Shop is slow in wp-admin. Use xSpeed Hub to check the object cache before anything else.
- With xSpeed Hub, test Redis on shop, and if it passes, turn the object cache on.
- Ask xSpeed Hub for the wp-config.php object cache snippet for docs.
- Use xSpeed Hub to flush the object cache on blog. Old options survive a page cache purge.
- With xSpeed Hub, turn the object cache off on shop and confirm the drop-in is gone.

## Frequently asked questions

### Can Muse check Redis without being able to change anything?

Yes. Turn on Read-only everywhere for the connection token Muse sends. The status and test tools are reads and keep working, while the Hub refuses toggle_object_cache and flush_object_cache.

### Should I ask Muse for the wp-config snippet?

Avoid it. The snippet can contain the saved Redis password, and Meta notes that what Muse has used may stay in its memories and your conversation history. Let the site write the constants into wp-config.php when the object cache is enabled, or add them yourself from your host's details.

### Why test the connection before turning the object cache on?

Because a cache server that does not answer costs time on every request while the page cache still looks fine. The Hub tells the agent to run test_object_cache first, and the site also tests the connection when you enable and refuses to continue if it fails. The probe is still worth running on its own, since it returns the server's exact reason, such as a wrong password or a refused connection.

### What happens if Redis stops answering after I enabled it?

The site keeps working. The drop-in is built never to take the site down: it falls back to WordPress's own cache for the length of the request and marks itself as degraded. A request can still wait up to the connection timeout, which is 1 second by default, so the site gets slower. xSpeed reports that state as degraded, and test_object_cache names the fault.

### Can the agent install Redis for me?

No. These tools connect xSpeed to a Redis or Memcached server that already exists and switch the object cache on or off. Getting a server is a hosting task. xSpeed uses the phpredis extension when it is there and its own built-in client when it is not.

### What is the difference between flush_object_cache and purge_cache?

flush_object_cache empties the persistent object cache and nothing else. purge_cache with type object does the same job through the purge tool, and purge_cache with type all also clears the page cache and, when connected, the Cloudflare edge. Use the flush when stale options or transients survive a page cache purge.

### Is the wp-config.php snippet safe to share?

Treat it like a secret. The snippet is built from the settings saved on the site, so it can contain the Redis password if one is saved. Paste it into wp-config.php yourself and avoid sharing it in a chat or a ticket.

## Set up Redis object cache with other agents

[Claude Code](https://xspeedcache.com/agent/claude-code/object-cache/) · [Claude](https://xspeedcache.com/agent/claude/object-cache/) · [Claude Cowork](https://xspeedcache.com/agent/claude-cowork/object-cache/) · [ChatGPT](https://xspeedcache.com/agent/chatgpt/object-cache/) · [Codex](https://xspeedcache.com/agent/codex/object-cache/) · [Cursor](https://xspeedcache.com/agent/cursor/object-cache/) · [GitHub Copilot in VS Code](https://xspeedcache.com/agent/github-copilot/object-cache/) · [Windsurf](https://xspeedcache.com/agent/windsurf/object-cache/) · [Gemini CLI](https://xspeedcache.com/agent/gemini-cli/object-cache/) · [Antigravity](https://xspeedcache.com/agent/antigravity/object-cache/) · [Zed](https://xspeedcache.com/agent/zed/object-cache/) · [Kiro](https://xspeedcache.com/agent/kiro/object-cache/) · [OpenCode](https://xspeedcache.com/agent/opencode/object-cache/) · [OpenClaw](https://xspeedcache.com/agent/openclaw/object-cache/) · [Hermes Agent](https://xspeedcache.com/agent/hermes-agent/object-cache/) · [Grok Build](https://xspeedcache.com/agent/grok-build/object-cache/) · [ChatGPT dots](https://xspeedcache.com/agent/chatgpt-dots/object-cache/) · [Grok](https://xspeedcache.com/agent/grok/object-cache/) · [Grok Bot](https://xspeedcache.com/agent/grok-bot/object-cache/) · [Manus](https://xspeedcache.com/agent/manus/object-cache/) · [Kimi Code](https://xspeedcache.com/agent/kimi/object-cache/) · [Paperclip](https://xspeedcache.com/agent/paperclip/object-cache/) · [NanoClaw](https://xspeedcache.com/agent/nanoclaw/object-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/)
- [Warm the WordPress cache with Muse](https://xspeedcache.com/agent/muse/preload-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 enable Redis or Memcached: https://xspeedcache.com/docs/object-cache/
- How to enable Page Cache: https://xspeedcache.com/docs/page-cache/
- Common problems and troubleshooting: https://xspeedcache.com/docs/common-problems-and-troubleshooting/