How operators run Grok Bot after week one

Fetched and re-checked against public posts through 2026-09-04, plus a fresh X pass on 2026-09-04. Isolation is still per user. Screens are not a fence. Official packages stay on x.ai/bot.

1. Kill the mega-chat

Johnny Nel’s job-board post puts it in one line: one Chief of Staff plus specialists, not one mega-chat. Each Bot is a job, not a whole company. Nate’s getting-started videos make the Chief of Staff refuse specialist work — otherwise everything bottlenecks through one agent. Debbie’s notes: start with one door, let it propose the team, do not open a Bot for every sub-task.

If your sidebar is already a crowd, the first operator job is an audit, not a new hire. Ask the pinned Bot to list every teammate, the last useful output, and what to merge. That is Debbie’s move: turn the Chief of Staff on the roster you already built.

You are the only Bot I talk to. Before you do a task, check whether another Bot already owns it and delegate. Only do the work yourself if no specialist fits. Bring results back here.

Keep a what’s-left page in /workspace. For each item: owner Bot, source, next step, whether I owe a decision.

Never: send email or posts, create or delete Bots, pay, or invent a “done” if a specialist produced nothing.

Sources: Johnny Nel · Debbie · Nate’s CoS description as shown in public walkthroughs (delegate first). Official PM guide: Grok Bot for PMs.

2. One job per Bot — then stop using it as chat

s1rozha’s field note: Email Bot on a 7:30 timer, sponsor-lead labels on another timer, calendar Bot separate. The trick is stopping using Grok Bot as chat. Ben Lang’s internal list (quoted in community follow-ups) and Johnny’s board add a second artifact: a Notion or /workspace page you can ask “what’s left.”

Create or update /workspace/whats-left.md. One row per open item: date, owner Bot, source (link or path), status, what you need from me. Do not start new work that is not on this page. If a specialist stalled, retry once, then flag me.

Sources: s1rozha · Johnny Nel · Ben Lang.

3. Teach once. The skill is still a draft

Official Teach a task: demonstrate up to about ten minutes of screen, no microphone, then review the skill the Bot wrote. mrfundman used it on a real WordPress update instead of writing a deploy script first. Community tips posts converge on the same order: do the thing once, never start from a 2,000-word prompt.

The learned skill is a draft. Add when to use it, what “done” looks like, what happens if the source is missing, and what must be approved. Then test on a different safe input. Details and the copyable template: skills and routines.

Sources: official skills docs · mrfundman · ReallyPhant tips.

4. Routine only after two good runs

KC’s widely bookmarked “Hiring is easy / managing is the skill” post says most multi-bot setups go quiet after 10–14 days. Treat that as a warning, not a measurement we repeated. The operator fix in official docs is boring: Test run does real things; cap is 50 routines per Bot; keep the latest 20 runs; delete has no undo.

s1rozha and the YouTube “support Bot via routines” demo both schedule after the method exists. Event triggers (Slack / GitHub) are not the same as installing those plugins. Working hours beat 24/7 browsing if you care about the weekly pool — usage and On-Demand.

Sources: KC · routines support demo · official routine example in xAI docs.

5. Connectors first. Money stays with you

Wayne Sutton’s site-from-the-phone post used Convex and Cloudflare plugins, not a cloud-browser shopping spree. Gergely Orosz connected support mail and Stripe and still required a human before money moved. Official @bot later shipped Stripe Link the same way: the Bot raises a spend request; you approve; a one-use card appears.

Darian Shirazi’s refund chase is the same shape: find the work, draft the mail, do not treat the author’s fee comparison as our number. Installed connectors are account-level — every Bot can see them. How to add remote MCP (not localhost): plugins.

Sources: Wayne Sutton · Gergely Orosz · @bot Stripe Link · Darian Shirazi.

6. Put memory in /workspace, not in chat

RefoundAI’s first-week writeup: standing rules in the Bot description, source-of-truth files, a daily plan that cites sources, then a routine. Logos52 publishes weekday dumps of what a fleet writes under /workspace. jblack4vols keeps dated decision logs per Bot. That is how you survive the 10–14 day fade: the next run reads a file, not last Tuesday’s chat.

The computer is still one machine. Lee Robinson and Logan’s posts are design notes — thin client, always-on box, browser as a tool — not a license to treat a second Bot as a fence. Shared-computer lesson: one computer per user.

Sources: RefoundAI · Logos52 packets · jblack4vols logs · Lee Robinson.