# Set up the Redis object cache with Windsurf

> Setting up a Redis object cache with Windsurf means asking its agent to check a site's object cache, test the Redis connection and enable it through xSpeed Hub.

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

You are in Windsurf, which now ships as Devin Desktop, with its agent open next to the code of a WordPress site. Type: set up Redis for shop and test it first. The agent calls get_object_cache_status through xSpeed Hub and reports the object-cache.php drop-in state, the configured backend and its stats. It does not tell you whether Redis is reachable, so the status is only the starting point.

The next call is test_object_cache. The site's plugin connects to its Redis server, writes a probe value and reads it back, and a failure returns the server's own message: wrong password, refused connection or permission denied. When it passes, the agent calls toggle_object_cache with enabled set to true to install the drop-in. The Devin Local agent prompts before it calls any MCP tool, so the toggle is something you accept or decline in the editor. You can allow one tool or the whole xspeedhub server, for the session or permanently, and permission rules such as mcp__xspeedhub__test_object_cache allow, deny or always ask for a named tool.

Windsurf's own difference is that it is in transition. The Devin Local agent and the older Cascade agent are set up differently, so the menus and names you see depend on which one you use, while the tool names in the calls stay the same. Cascade also caps the tools it loads at 100, so before you start, check that the four object-cache tools are listed. The editor runs on your machine, so rely on test_object_cache rather than a local redis-cli for the Redis check.

## Set up Windsurf 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 for the Devin Local agent

Run this in a terminal. Devin Local shares its MCP configuration with Devin CLI, and -s user saves the server to ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows) so it applies to every project. Without -s, the command saves to local scope, which is the current project only.

```bash
devin mcp add -s user xspeedhub https://app.xspeedcache.com/xspeed/mcp
```

### 3. Sign in

Run the login command and approve access on the xSpeed Hub page that opens in your browser. There is no token to paste, and the client keeps the credentials it receives. If the server later shows Needs auth in the Devin Local MCP list, click Authenticate, or run devin mcp logout and then login again.

```bash
devin mcp login xspeedhub
```

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

### 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. The Devin Local agent prompts for approval before it calls any MCP tool. In the prompt you can allow that one tool or every tool on the xspeedhub server, for this session or permanently, and permission rules such as mcp__xspeedhub__get_cache_status allow, deny or always ask for a named tool. Smart mode lets a fast model run what it judges safe without a prompt, and Bypass mode approves everything, so with either of those a write reaches the Hub as soon as your connection allows writes. xSpeed Hub has no confirmation step of its own.

## Prompts

- Use xSpeed Hub to check the object cache on shop, run the Redis test, and tell me what each result means.
- With xSpeed Hub, enable the object cache on shop if the Redis test passes, and read the status back.
- List the four object cache tools you have from xSpeed Hub before you start.

## Example session

```
You: Use xSpeed Hub to set up Redis for shop. Run the connection test first.
  → get_object_cache_status(site: shop) [read-only]: Drop-in not installed. Backend: Redis configured.
  → test_object_cache(site: shop) [read-only]: Connected. Probe value written and read back.
Agent: Redis answers. May I enable the object cache on shop?
You: Yes.
  → toggle_object_cache(site: shop, enabled: true) [changes site]: Drop-in installed. Redis is on.
Agent: Done. Redis is now the object cache for shop.
```

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

Allow the two reads for this job by name and leave the writes on the prompt. The Devin Local agent prompts before any MCP tool by default, but allowing the whole xspeedhub server removes the prompt before toggle_object_cache too. So do Smart mode, where a fast model runs what it judges safe, and Bypass mode, which approves everything. The Hub does not confirm writes itself.

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

### Does Windsurf becoming Devin Desktop change how I set up Redis?

Not the steps. The object-cache tools and their order stay the same: status, then test_object_cache, then toggle_object_cache. What changes is the menus and the agent you connect, so check whether you are in Devin Local or legacy Cascade.

### Will Windsurf stop before it toggles the object cache?

In the Devin Local agent it does by default, because that agent prompts before it calls any MCP tool. If you allowed the whole xspeedhub server, or you use Smart or Bypass mode, the write reaches the Hub as soon as your connection allows writes, because the Hub has no confirmation step of its own. While you diagnose, connect with the connection token and Read-only everywhere on, or sign in as a Viewer member.

### 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/) · [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/) · [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 Windsurf

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