Most small-business mornings start the same way: an inbox full of overnight messages, a calendar that is already tight, and a few quotes nobody has chased. xAI’s Grok Bot is built for exactly this kind of recurring work. The question is not whether it can draft a morning brief, but how you set it up so it runs on schedule and never acts without your yes.
What Grok Bot is and who can use it
xAI introduced Grok Bot as a beta on 11 August 2026. It is a team of always-on agents: software assistants that take a task, work through the steps on their own and come back when something needs your approval. At launch it ran on desktop and iOS and was included with SuperGrok, SuperGrok Plus and SuperGrok Heavy, with Cursor Pro, Pro+ and Ultra, and with Cursor Teams Standard and Premium. Enterprise customers could join a waitlist. One detail matters for budgeting: bots have their own usage, separate from your Grok or Cursor plan.
Bots sign in to the tools you already use, such as inboxes, CRMs, websites and apps. xAI stresses that this includes platforms with no clean API or MCP, the standard interfaces that normally connect AI tools to other software. In practice the bot uses the website the way you would.
What “its own computer in the cloud” means
Each account gets one persistent cloud computer. Every bot on that account uses it and shares its files, browser sessions and logins, which is how one bot can hand work to another. Because the work runs there, closing the app, your laptop or your phone does not stop a background task or a scheduled routine.
That is the real reason a “chief of staff” bot can work around the clock: the brief is prepared on a machine that is still on while yours is off.
Setting up a morning brief and an evening wrap-up
A routine tells one bot when to run a workflow. It can run on a schedule or when something happens: a Slack message, a GitHub, Linear, Sentry or PagerDuty event, an email to the bot’s own address, or a webhook call. Only new activity counts, so events from before the trigger existed do not start a run. You can also show a bot a task once and let it save the steps as a routine, then correct it.
You do not need a settings page to create one. You ask the bot that should own the job in chat, and it creates or changes the routine. A practical sequence looks like this:
First, describe the jobs in one message: a short brief at 7:00 with today’s priorities, inbox sorting with drafted replies, a list of open follow-ups and an end-of-day summary. Second, check the time zone. Schedules follow the Timezone setting under Bot in Settings, which auto-detects from the computer, and you can set a different zone for a single routine. Third, use Test. A new routine waits for its next scheduled time, so Test is the only way to see tomorrow’s brief today.
The limits are generous for this use: a bot can own up to 50 routines, schedules must be at least five minutes apart, and the app keeps the 20 most recent run records for each routine.
One bot as chief of staff, others as specialists
xAI’s own announcement describes this pattern: a chief-of-staff bot overseeing specialist bots. Bots can message each other, share context in threads and pass ownership of a task, for example from an engineering bot to a debugging bot. So a coordinating bot that asks a marketing bot for a draft and reviews it before showing you fits the documented design. The documentation does not say whether a bot can create another bot by itself, so treat that as something to check in your own account rather than a promised feature.
Keeping the final yes
Writing “never send anything without my approval” into the setup message is a good start, but Grok Bot also has controls that do not depend on the bot remembering an instruction. Whether an action needs approval depends on the tool, the risk of the action and your Auto-review rules. You can add narrow “Ask first” rules for sending, publishing, deleting, purchasing or changing production systems.
Here is the detail I would plan around: approvals requested by work that started without you, such as a routine, expire after about 30 minutes. If the 7:00 brief drafts replies and you only open the app at 8:30, those requests may have lapsed. I would rather schedule the brief for the moment you actually sit down, and set “Ask first” for sending before the first run. That keeps the approval step a real decision instead of a backlog. Who takes the next step? With this setup, always you.
Limits and risks for a small business
The shared computer is the trade-off. Because all bots share files, browser sessions and logins, xAI warns against treating separate bots as a security boundary. A “marketing bot” and a “finance bot” are a way to organise work, not a way to separate access. Only sign in to accounts you are comfortable with every bot on that account reaching.
Logins work through Vault, a connected password manager or a Secure Form, so the bot does not see the values. Single sign-on, passkeys and CAPTCHAs need you to take over the computer. Some websites block traffic from cloud computers; in that case the bot hands the step back to you, or you can route its traffic through your own computer in Settings.
For a roofer, a clinic or an agency, the sensible first version is small: one coordinating bot, two scheduled routines, strict “Ask first” rules and only the logins it truly needs. Add specialist bots once the morning brief has proven useful.
