Set up the Redis object cache with OpenClaw

Setting up a Redis object cache with OpenClaw means asking the always-on agent to check a site's object cache, test the Redis connection and enable it through xSpeed Hub.

get_object_cache_statustest_object_cacheget_settingsupdate_settingstoggle_object_cacheflush_object_cache

Last updated: October 2026

Example session · OpenClaw

You: With xSpeed Hub, set up Redis for shop. Status, then test, and wait for my yes.

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.

OpenClaw: The test passed. Enable the object cache on shop?

You: Yes.

toggle_object_cache(site: shop, enabled: true) changes site
→ Drop-in installed. Redis active.

OpenClaw: Redis is on. Want a morning automation that runs only the Redis test and reports failures?

How OpenClaw handles this

You are talking to OpenClaw, the agent that stays running, and you want Redis behind the object cache of the shop site. Say so: set up Redis for shop, status first, then test, and wait for my yes. OpenClaw calls get_object_cache_status through xSpeed Hub, which reports whether the object-cache.php drop-in is installed, which backend is configured and its stats. It does not prove that Redis answers, so test_object_cache follows it.

The test makes the site's plugin connect to the Redis server and read and write a probe value, and a failure returns the server's own error. A pass is when OpenClaw can call toggle_object_cache with enabled set to true. Do this part in a live conversation. Enabling also writes the connection constants into wp-config.php, and a failed test should end with you deciding what to fix, not with the agent trying other things on its own. A per-server tool filter can also leave toggle_object_cache and flush_object_cache out of the agent's reach until you want them.

What OpenClaw adds is automations. Once Redis is on, an automation can call get_object_cache_status and test_object_cache every morning and report to you only when the test fails, which catches a host that rotated the Redis password. The Hub has no scheduler for agent prompts, so that timer lives in OpenClaw. Keep what runs by itself to reads, and keep the toggle and any flush for conversations where you are present. A flush empties the cache and the next requests rebuild it from the database, so it is worth watching.

Set up OpenClaw once

Already connected? Skip to the prompts. Alternatives and troubleshooting are on the OpenClaw 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.

2Save xSpeed Hub as an MCP server

Run this on the machine that hosts your OpenClaw Gateway. Set the transport to streamable-http: OpenClaw falls back to SSE when you leave it out. With --auth oauth the command saves the server without a connection test, because sign-in has to happen first.

Terminal

openclaw mcp add xspeedhub \
  --url https://app.xspeedcache.com/xspeed/mcp \
  --transport streamable-http \
  --auth oauth

3Sign in with openclaw mcp login

OpenClaw prints an authorization URL and listens on a loopback address for the callback. Open the URL, sign in to xSpeed Hub and approve; the token exchange finishes by itself. There is no token to paste. If your browser is on another machine, copy the code from the redirect and pass it back with openclaw mcp login xspeedhub --code. Then check the connection.

Terminal

openclaw mcp login xspeedhub
openclaw mcp doctor xspeedhub --probe

1 / 3

Full OpenClaw 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. OpenClaw gives you two client-side gates, and the Hub adds none. First, openclaw mcp tools xspeedhub --include limits which tools exist for the agent, so a list of read tools keeps every write out of reach. Second, when the Codex runtime runs your agent turns, MCP tool approvals follow the session's permission posture, and the default full-permission posture does not prompt. openclaw mcp configure xspeedhub --approval prompt asks on every call, and Allow Always saves a grant for that one tool with any arguments. OpenClaw's docs describe that per-call prompt for the Codex runtime; with its own embedded runtime, use the tool filter to decide what the agent can call. The Hub has no confirmation step of its own.

What do I ask?

Three prompts written for OpenClaw. More for this job are below.

Prompt for OpenClaw

Use xSpeed Hub to set up Redis object cache on shop: status, then test, and wait for my yes before you enable.

Prompt for OpenClaw

Every morning, ask xSpeed Hub to run test_object_cache on shop and report to me only if it fails. Do not change anything.

Prompt for OpenClaw

Using xSpeed Hub, check whether the object cache on blog is still enabled and the Redis test still passes.

What happens, step by step

A persistent object cache keeps database query results in Redis or Memcached instead of rebuilding them on every request. Through xSpeed Hub an agent can read the state of the cache, probe the cache server, switch the cache on or off, and flush it. The Hub tells the agent to run the probe first, because the status call alone does not prove the server is reachable.

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.

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.

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.

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.

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.

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 worth keeping

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 OpenClaw

An automation is the risky place for this job. A scheduled run is unattended, so nobody is present to approve toggle_object_cache or flush_object_cache, and the Hub runs a write as soon as the connection allows writes. Keep setup in a live conversation. Give the job a tools allowlist of xspeedhub__get_object_cache_status and xspeedhub__test_object_cache, or use the connection token with Read-only everywhere on (or a Viewer sign-in), so that only the two reads work. The default full-permission posture of the Codex runtime does not prompt, so the tool filter is the gate that matters.

More prompts for this job

They work in any client connected to xSpeed Hub.

Prompt

Using xSpeed Hub, is a persistent object cache running on shop, and which backend does it use?

Prompt

Use xSpeed Hub to test whether Redis is reachable from shop. Do not change anything.

Prompt

Shop is slow in wp-admin. Use xSpeed Hub to check the object cache before anything else.

Prompt

With xSpeed Hub, test Redis on shop, and if it passes, turn the object cache on.

Prompt

Ask xSpeed Hub for the wp-config.php object cache snippet for docs.

Prompt

Use xSpeed Hub to flush the object cache on blog. Old options survive a page cache purge.

Prompt

With xSpeed Hub, turn the object cache off on shop and confirm the drop-in is gone.

Frequently asked questions

Yes, OpenClaw can run automations, so a scheduled run can call test_object_cache and report a failure. The Hub has no scheduler for agent prompts, so the schedule lives in OpenClaw. Keep the scheduled run to reads.

No. An automation runs unattended, so nobody is there to approve it. A line in the prompt telling the agent not to write is guidance, not a lock. Give the job a tools allowlist of the two reads or filter the write tools out of the server, and use the connection token with Read-only everywhere on, or a Viewer sign-in, if you want the Hub itself to refuse a write.

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.

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.

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.

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.

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, from OpenClaw.

xSpeed Hub is free and has no site cap. Connect your sites once and ask from the agent you already use.

Open xSpeed Hub OpenClaw setup

Set up the Redis object cache with OpenClaw

How OpenClaw handles this

Set up OpenClaw once

What do I ask?

What happens, step by step

Reference

Rules worth keeping

More prompts for this job

Frequently asked questions

Keep going

Set up Redis object cache, from OpenClaw.