Manage servers with Grok Bot on xCloud

A server question rarely arrives at a convenient moment, and a Bot is the teammate that is already on. You message it from your phone: which of my servers is above 80% disk. The Bot attaches xcloud, calls servers_index and servers_monitoring and answers with CPU, RAM and disk in a short table, flagging statuses such as low disk space or reboot required. Monitoring history is a paid-plan feature, so on the free plan the answer says it is a plan limit, not a missing permission. Bots keep stable preferences in memory, so you can tell the hosting Bot once which server is production and which services must never be disabled, and later requests start from that.

Changes come in two kinds. Reads and routine actions run straight away: the Bot can restart a service with servers_services_restart without an xCloud prompt, and it should still name the server, the service and the impact first. Anything that can interrupt a server, such as a reboot, a runtime change, a firewall rule or a sudo user, stops for an explicit confirmation, and Grok Bot shows its own card as well. A reboot is tracked: the Bot calls servers_reboots_store, then reads servers_reboots_show until xCloud reports a verified new boot, and an unconfirmed result is investigated, never repeated. The Bot also reads servers_tasks until each accepted change settles, because xCloud returns before the work finishes.

A morning routine is where Grok Bot earns its place. Ask for one: every weekday at 8:00 AM, list my servers with CPU, RAM and disk, flag any above 80% disk or showing reboot required, and post here. It runs while your laptop is closed, you Test run it first, and recent runs sit under Routines in the conversation details. It reports. It never reboots or restarts on its own. Buying, resizing and deleting servers are different again: a purchase needs an approved plan, region and price, while resizing and deleting a server are dashboard-only.

Grok Bot specific: Set Ask first rules for server changes before you hand a Bot a server. Auto Review, under Settings, General, Auto-review, takes Ask first and Allow automatically rules, and Ask first wins, so a rule that names reboots, service changes and firewall rules keeps the card in front of you in your own chat even if you once chose Always allow. Personal rules are stored on your desktop, though, and in a Slack channel or group chat where nobody can answer a card a Team Bot runs without Auto-review and stays within the permissions it was set up with, unless your team admin enforces Auto-review. xCloud's own confirmation still stops a reboot, a runtime change, a firewall rule or a sudo user in any conversation, but restarting or enabling a service has no xCloud prompt, so for a Team Bot that works in channels either have the admin enforce a team Ask first rule for service changes or connect its xCloud plugin Read-only and keep service changes in a 1:1 chat. Disabling ssh, nginx or a database can lock you out or take sites offline, so ask the Bot to say what a change will do before you answer, and write the same boundary into the Bot's description so it applies in every chat.