# Set up the Redis object cache with Grok Bot

> Setting up a Redis object cache with Grok Bot means giving one of xAI's named Bots the care of a site's object cache, from the first test and enable through xSpeed Hub to flushing it when stale data survives.

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

Your Grok Bot set up Redis on shop a month ago and has looked after it since. Today a store notice you removed still shows on the storefront, even after a page cache purge. You attach the xspeedhub plugin with @ and ask the Bot to find out why. It calls get_object_cache_status, which reports that the object-cache.php drop-in is installed and connected to Redis, and from that it works out where the old notice most likely lives: in an option or transient that Redis is still holding.

What comes back is a proposal with its cost. flush_object_cache empties the persistent object cache on shop, so the old notice goes, and the next requests rebuild their data from the database and run a little slower until the cache fills again. A flush does not touch the page cache; purge_cache does that. The Hub tells the agent to briefly confirm intent first, and Grok Bot itself offers Allow once, Always allow or Deny when an action needs approval. Choose Allow once, then reload the page logged out. If the notice survives a flush too, it is stored in the database itself.

What differs in Grok Bot is the persistent cloud computer. It has a terminal, but that terminal runs in Cursor's cloud, not on your web server, so a redis-cli ping from it says nothing about the Redis your site uses. test_object_cache is the check that counts, because it runs from the site's own server. The cloud computer is still useful for routines: ask the Bot for a weekly run of get_object_cache_status and test_object_cache that posts only when the test fails, and it runs while your laptop is closed.

## Set up Grok Bot 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. Ask your Bot to add xSpeed Hub

In a chat with your Bot, ask it to add a custom remote HTTPS MCP server with this URL. xAI says a plugin you add from your own chat is personal and account-wide, so every Bot on your account can use it. When the browser opens, approve access on the xSpeed Hub page.

```
Add a custom remote HTTPS MCP server called xspeedhub with the URL https://app.xspeedcache.com/xspeed/mcp and sign me in.
```

### 3. Attach it and ask a first question

Type @ in a chat to attach the xspeedhub plugin to the task, then ask something that names xSpeed Hub. A list of your sites means the connection works.

```
Use @xspeedhub (xSpeed Hub) to list my sites and tell me which ones have page caching turned off.
```

Full setup: https://xspeedcache.com/agent/grok-bot/

### 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. When an action needs approval, Grok Bot offers Allow once, Always allow or Deny. Always allow saves a rule, so the same kind of call no longer stops for you. Auto-review rules under Settings, General, Auto-review can force Ask first or allow matching actions automatically, and Ask first wins when both match. xSpeed Hub has no confirmation step of its own, so a Hub write tool you always allow runs as soon as your connection allows writes. Add Ask first rules for purge_cache, update_settings, toggle_cache, optimize_site and the other write tools. For read-only access, sign in as a Viewer member of the workspace.

## Prompts

- Use @xspeedhub (xSpeed Hub) to find out why a removed notice still shows on shop after a page cache purge.
- Every Monday, use xSpeed Hub to test Redis on shop and post only if the test fails. Report only.
- With xSpeed Hub, test Redis on blog and enable the object cache if it passes, asking me first.

## Example session

```
You: Use @xspeedhub (xSpeed Hub) to find out why the notice I removed still shows on shop after a page cache purge.
  → get_object_cache_status(site: shop) [read-only]: Drop-in installed. Backend: Redis, connected.
Agent: The page cache is clear, so the old notice is most likely an option or transient that Redis still holds. Flushing the object cache on shop clears it, and the next requests rebuild from the database a little slower. Flush it?
You: Yes, flush it.
  → flush_object_cache(site: shop) [changes site]: object cache flushed
Agent: Flushed. Reload the page logged out. If the notice is still there, it is stored in the database itself, not in the cache.
```

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

Always allow on flush_object_cache or toggle_object_cache saves a rule, so the next flush runs without stopping, and xSpeed Hub has no confirmation step of its own. Add Ask first rules for both under Settings, General, Auto-review, since Ask first wins over an automatic allow. xAI notes that a routine's Test run performs real work, so test a routine with a report-only prompt. For a Bot that should only watch, sign in as a Viewer member so the Hub refuses every write.

## 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 a Grok Bot check Redis from its own terminal?

Not usefully. The Bot's terminal runs on its cloud computer, not on your web server, so a ping from there says nothing about the Redis your site uses. Ask it to run test_object_cache through xSpeed Hub instead, which probes Redis from the site's own server.

### When should a Grok Bot flush the object cache?

When stale options or transients survive a page cache purge, such as a notice you removed that still shows. A flush empties the object cache only, and the site rebuilds the data on the next requests. Allow it once rather than always, because the Hub runs the flush as soon as it is called.

### 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/) · [Muse](https://xspeedcache.com/agent/muse/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 Grok Bot

- [Purge the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/purge-cache/)
- [Find out why WordPress pages are not cached with Grok Bot](https://xspeedcache.com/agent/grok-bot/troubleshoot-cache/)
- [Scan a website for speed problems with Grok Bot](https://xspeedcache.com/agent/grok-bot/speed-scan/)
- [Run and track PageSpeed tests with Grok Bot](https://xspeedcache.com/agent/grok-bot/pagespeed-tests/)
- [Raise a WordPress site's PageSpeed score with Grok Bot](https://xspeedcache.com/agent/grok-bot/optimize-site/)
- [Tune WordPress cache settings with Grok Bot](https://xspeedcache.com/agent/grok-bot/cache-settings/)
- [Warm the WordPress cache with Grok Bot](https://xspeedcache.com/agent/grok-bot/preload-cache/)
- [Manage Cloudflare caching with Grok Bot](https://xspeedcache.com/agent/grok-bot/cloudflare/)
- [Manage every WordPress site at once with Grok Bot](https://xspeedcache.com/agent/grok-bot/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/