GrokBot Table of Contents

Thirteen field-note pages. Read them as a desk, not a pile. Weekend path first, then the catalog, then Grok Build (different product).

← AI Agents · Productivity · Product overview · Grok Build (not Bot)

Weekend path (do this first)

Four pages. One sitting. Enough to stand up a desk without lighting the weekly meter or auto-tweeting.

/grokbot — what the product is (Riley walkthrough + 100 use cases). Skim; don’t memorize the list.
/grokbotfieldmanual — the operating system. One shared VM, Chief first, teach → skill → routine, send/spend/publish behind approval.
/grokbottips — Require Approval (Auto-review), six named bots, herdr so you don’t compile on the Bot meter.
/grokbotceo — one inbox over specialists. Reverse-prompt the roster. Don’t invent five bots on day one.

Then, if you already have a Grok Bot sub and it is eating the week: /grokbotlimits. If you want the official workshop before the desks: /grokbotcourse.

All 13 GrokBot pages

Learning order, not publish order. “Steal this” is the one line to keep if you only open the page once.

	Page	What it is	Steal this
1	/grokbot	Product + 100 beta use cases (Riley + Zakariasson)	Bot = job, not a mega-chat. Grok Bot for the fleet, Grok Build for the repo.
2	/grokbotfieldmanual	Rev 1.2 carousel, transcribed (@RoundtableSpace / @Argona0x)	Screens ≠ security. Ladder never skips a rung. Batch syncs or 12× quota.
3	/grokbottips	Ben Lang 10 tips, Corey six-bot desk, Ennis herdr + lantern	Require Approval beats Always Allow. Don’t cron every 5 minutes.
4	/grokbotceo	Teslaconomics Chief-of-Staff pattern	Specialists first, one CEO inbox routes and packages. Description survives; chat scrolls.
5	/grokbotcourse	Official SpaceXAI/Cursor workshop (Amrita) + full ASR	Teach a skill, never schedule attempt #1, always ask first on outbound.
6	/grokbotlimits	Aaron Makelky: 64% of a week gone in two days	Install Cursor/Codex/Build on the bot VM. herdr the panes. Bot only coordinates.
7	/grokbotteam	Lauren Tan (@poteto) × Colin Matthews, ~56 min + ASR	Verification + feature map, then hard CI. Overlay “15–25 bots” is not this talk.
8	/grokbotsocial	Alex Finn always-on social / multi-brand	One bot per brand + a CEO. Not one mega social bot.
9	/grokbotx	Daniel Ch 3-account X loop (via @Voxyz_ai)	Human still hits publish. Latency ≠ stall; don’t double-post.
10	/grokbothedgefund	Roan six-bot overnight research desk	Producer ≠ reviewer. Research layer, not a trading system.
11	/grokbotseoagent	Sarvesh 20 local-SEO prompts, mapped to RankingSolution	Named SEO bot, GSC page-2 sprint, DataForSEO not Ahrefs-in-Chrome.
12	/grokbotericsiu	Eric Siu: Grok Bot vs Hermes vs OpenClaw + ASR	Easier cloud on-ramp. Keep Hermes/Codex. SEO last mile is human.
13	/grokbotelon	Viral “Elon / GrokBot #1” overlay vs xAI all-hands + ASR	GrokBot is never named in the talk. Overlay ≠ source.

If you only have an hour

Goal	Open
Stand up a desk tonight	field manual week-one checklist + CEO
Stop the quota furnace	limits then Ennis on tips
Don’t auto-tweet / auto-email	tips tip 6 (Require Approval) + gymhack
Social / X	social then X loop
SEO	SEO agent then seoloop (RankingSolution)
Research swarm	hedge fund (maker-checker) + field manual swarm rules
Should I uninstall OpenClaw?	Eric Siu — no; Grok Bot is the cloud on-ramp
Long workshop with transcript	course (Amrita) or team (Lauren)

Adjacent (not Grok Bot, but the same desk)

SEO loop → RankingSolution — Access / Action / Memory / Judgment / Reversal
Gym hack — what write access looks like with no fence
Chief of staff · God agent vs team
Codex Fast vs Medium — the other usage knob
ChatGPT Work — the other knowledge-work surface
BlockChannel — Auto-review’s protocol cousin
Grok Build (coding CLI, different product): /category/grok-build · /grokbuild · /grokthreads · /grok-mobile · /grok-cursor

Alphabetical

bot · ceo · course · elon · ericsiu · fieldmanual · hedgefund · limits · seoagent · social · team · tips · x

Field notes · August 2026 · 13 pages · One boring job tonight · start with the manual