Deploy from Git with Grok Bot on xCloud

A Bot is a teammate with a name and a job, so the cleanest setup is one Bot whose description says it owns hosting. You open it from the desktop app or from your phone, type @xcloud to attach the connector to the task, and send a line such as: deploy github.com/example/shop to my Frankfurt server on a staging hostname and show me the dry run first. The Bot calls git_detect and reports what xCloud found: the app type, the branch, the install, build and start commands, the web root and any warning. Because the Bot works on a cloud computer and calls xCloud from there, it never looks at a folder on your laptop. The repository has to be reachable by xCloud itself, which means a public URL, a repository on a Git provider connected to your xCloud team, or a private one with a deploy key the Bot helps you set up.

Approval happens twice, on purpose, and it helps to know which is which. xCloud will not create a site without an explicit confirmation, so after the dry run the Bot asks you in plain words and only then sends the confirmed create call through servers_sites_git_auto. Grok Bot adds its own approval card for the tool call, with Allow once, Always allow and Deny. Choose Allow once for a deploy. The Bot then polls sites_status, tells you each real change on the way, and ends with the URL it fetched and the dashboard link xCloud returned. If you close the app halfway, the deploy carries on inside xCloud and the Bot picks the status up again when you ask. A failed build gets the same treatment on the same site: the Bot reads sites_deploy-diagnosis, proposes a correction and waits for your yes before it retries.

Memory and routines are where Grok Bot differs from a terminal agent. Tell the Bot once that production sites go on the Frankfurt server and staging sites on Singapore, and its memory keeps that preference between conversations. Then ask for a routine: every weekday at 8:00 AM, run detection and a dry run for github.com/example/shop and post any new warning here. A routine runs while your laptop is closed, but it can only detect and preview, because the create call waits for a yes from you. Use Test run before you rely on it, and open Routines under View conversation details to pause it or read its recent runs.

Grok Bot specific: The Bot cannot see your laptop, and that decides how deploys fail. Code you have not pushed does not exist as far as xCloud is concerned, so a Bot asked to deploy my project is deploying whatever the remote branch holds, not your working folder. Push first, name the branch and say which one you mean. Be careful with Always allow while you are learning, too: it can save a rule so Grok Bot's card no longer appears for that action, while the stop that matters for a deploy, the explicit confirmation xCloud demands before it creates a site, still arrives as a question in the conversation. If you want a hard stop before production, add an Ask first rule under Settings, General, Auto-review, and write the boundary into the Bot's description.