Grok Bot first-week checklist
The seven-day sequence we use for every setup: inventory, identities, build, cap, unattended. What to do each day and what to refuse.
Short answerDay 1 inventory and identities. Days 2–4 build and supervise. Day 4 cap. Days 5–7 first unattended runs with a watcher. Don't skip identities to get to the fun part; that's how everyone ends up with their Gmail on the shared computer.
This is a sequence, so it's numbered.
- Inventory (day 1). Every task you want off your plate; every tool it touches; what access each needs. Cross off anything that trades, moves money, posts as a person, or needs a login challenge defeated.
- Identities (day 1–2). One email per Bot. Seats and users in each tool with the narrowest role. Tokens created from Bot accounts. Your logins stay on your machine. Details.
- Shared computer baseline (day 2). Confirm nothing human is signed in. Create the Bots' working folder with a README. Cleanup.
- Build (day 2–4). One Bot per theme. One-time tasks first; make them reliable; save as skills; only then schedule. Supervised until three correct outputs each.
- Approvals (day 3). Per routine: never / always / threshold. Route approval summaries to Slack. Approvals.
- Cap (day 4). On-demand rule in the dashboard. Spend watcher routine at 60/85%. Kill procedure written and practised. No spend cap.
- Heartbeat (day 4). Every routine appends a line to a log on completion; a daily watcher reports missing lines.
- Unattended (day 5–7). First overnight runs. Read the morning message. Fix what drifted. Write the runbook.
- Changelog entry (day 7). What exists, what it may do, who to page.
If you'd rather we did it: Setup.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.