Manage WordPress with Grok Bot on xCloud

WordPress upkeep is mostly noticing: which of twelve sites has three plugin updates waiting, which has a new critical finding. A Grok Bot is built for noticing, because a routine can look every morning while your laptop is closed. Ask the Bot that owns hosting for the report and it uses the xcloud connector: sites_index to list your sites, sites_wordpress_refresh to refresh the cached plugin and theme list and sites_wordpress_updates to read what is pending for core, plugins and themes, grouped by site. None of that needs a prompt from xCloud, so the Bot can do it on a routine with nobody watching. It can also run sites_vulnerability-scan and read the counts by severity, and a PageSpeed scan covers mobile and desktop in one run.

Changes are where you come in. When the report says blog.example.com has three plugin updates, you reply with a go-ahead in the same conversation. The Bot sets backup_before_update to true for a production site and sends sites_wordpress_update for the plugin slugs you approved. In Grok Bot that shows up as an approval card, where you choose Allow once, and xCloud requires its own explicit confirmation as well. Updates run in the background, so the Bot confirms the result from the site's events and by loading the homepage, not from the response that said accepted. Put the standing rule where Grok Bot keeps it, in the Bot's description: client sites are never updated without my approval, and production gets a backup first.

Two things set this apart from a terminal agent. First, routine runs leave records, up to 20 per routine, so you can open Routines under View conversation details and compare this week's finding count with last week's. Second, a Bot can sit in a group chat. A magic login link from sites_magic-login is a password: it is single-use and expires after about ten minutes, but anyone who opens it is the admin. Ask for one in a private conversation with the Bot, not in a group chat where other people and Bots read it.

Grok Bot specific: A routine can find work but cannot finish it. Updating plugins, themes and core stops for an explicit confirmation, and so does a broken-link scan, so a routine that finds three updates reports them and then waits for you. Do not try to get around that by choosing Always allow on the update action and asking the Bot to update every morning. Grok Bot may stop showing its card, but xCloud still requires a confirmation for the update, and an update that nobody looks at afterwards is exactly what the backup-first habit exists to protect against. Keep the routine to refreshing, reading and scanning, and send the yes yourself when you have read the list.