Pinned Tweet
Grok Bot just became an engineering team
One SpaceXSI engineer's bots now run 200+ cloud agents at once, and the same app can call businesses, run your Shopify store and work the night shift
Here's how to build it in 10 steps:
Alex retweeted
Introducing a house of bots for your GrokBot - the same pattern the GrokBot team runs on
1 prompt + 0 code = you get the same:
• no more one giant bot that forgets why it exists - every bot does 1 job
• 1 chief of staff is your only contact - you never juggle 7 chats again
• 1 summary a day instead of checking every bot - done, stuck, needs your yes
here's how to set it up:
works on computer and phone*
1 → paste the prompt below into your main GrokBot - it becomes your chief of staff
2 → it asks what eats your week and splits it into jobs. 1 job = 1 bot (same rule Dr. Eggbot uses)
3 → it creates a focused bot for each job - each one gets 1 job, 1 voice and a "never do" list
4 → the whole team goes into 1 group chat - every handoff happens where you can see it
5 → if a new bot shows up disabled, hit Enable - that's your safety switch
6 → it sets a routine: morning board + evening summary. 1 message: what got done, what's stuck, what needs your yes
the result: you stop talking to bots and start reading 1 report. the chief routes, the bots work, you approve
p.s: the GrokBot eng lead runs her own house like this - a lead bot splits big projects, engineer bots build them as cloud agents and test before merging. full breakdown in the video
try it now. then read how Lauren's house works below 👇
Introducing a house of bots for your GrokBot - the same pattern the GrokBot team runs on
1 prompt + 0 code = you get the same:
• no more one giant bot that forgets why it exists - every bot does 1 job
• 1 chief of staff is your only contact - you never juggle 7 chats again
• 1 summary a day instead of checking every bot - done, stuck, needs your yes
here's how to set it up:
works on computer and phone*
1 → paste the prompt below into your main GrokBot - it becomes your chief of staff
2 → it asks what eats your week and splits it into jobs. 1 job = 1 bot (same rule Dr. Eggbot uses)
3 → it creates a focused bot for each job - each one gets 1 job, 1 voice and a "never do" list
4 → the whole team goes into 1 group chat - every handoff happens where you can see it
5 → if a new bot shows up disabled, hit Enable - that's your safety switch
6 → it sets a routine: morning board + evening summary. 1 message: what got done, what's stuck, what needs your yes
the result: you stop talking to bots and start reading 1 report. the chief routes, the bots work, you approve
p.s: the GrokBot eng lead runs her own house like this - a lead bot splits big projects, engineer bots build them as cloud agents and test before merging. full breakdown in the video
try it now. then read how Lauren's house works below 👇
Alex retweeted
holy f*ck, grok bot can pay for things now. shop pay checkout, buy now cards, order tracking
and xai already ships the bots that spend and save your money
the money bots:
→ travel coordinator - compares flights and hotels against your rules, confirms before booking, drops the trip in your calendar
x.ai/bot/sc693906bdeded166b7…
→ subscription cleaner - reads your receipt emails, suggests what to cancel, unsubscribes only from what you approve
x.ai/bot/sb36667ce9e1fdc00cf…
→ apartment scout - books apartment tours and applies to the listings you pick
x.ai/bot/sd6f165284d7fd2f25e…
→ expense manager - logs receipts from email and builds a weekly spend summary
x.ai/bot/s50bb9361d891bd788a…
→ haggle bot - inventories your software spend and hunts for savings
x.ai/bot/marketplace/bots/ha…
→ order concierge - buys with shop pay, then tracks the order to your door (templates tab in the app)
→ deal watcher - watches a price, pings you on the drop (templates tab in the app)
order concierge never places an order without your approval. deal watcher never buys. travel coordinator asks before every booking
start tonight: connect shop pay in vault → payments, add order concierge, then hand it the thing you were about to buy anyway
holy f*ck, grok bot can pay for things now. shop pay checkout, buy now cards, order tracking
and xai already ships the bots that spend and save your money
the money bots:
→ travel coordinator - compares flights and hotels against your rules, confirms before booking, drops the trip in your calendar
x.ai/bot/sc693906bdeded166b7…
→ subscription cleaner - reads your receipt emails, suggests what to cancel, unsubscribes only from what you approve
x.ai/bot/sb36667ce9e1fdc00cf…
→ apartment scout - books apartment tours and applies to the listings you pick
x.ai/bot/sd6f165284d7fd2f25e…
→ expense manager - logs receipts from email and builds a weekly spend summary
x.ai/bot/s50bb9361d891bd788a…
→ haggle bot - inventories your software spend and hunts for savings
x.ai/bot/marketplace/bots/ha…
→ order concierge - buys with shop pay, then tracks the order to your door (templates tab in the app)
→ deal watcher - watches a price, pings you on the drop (templates tab in the app)
order concierge never places an order without your approval. deal watcher never buys. travel coordinator asks before every booking
start tonight: connect shop pay in vault → payments, add order concierge, then hand it the thing you were about to buy anyway
Alex retweeted
SpaceXAI engineer Lauren Tan fixes bugs with seven short lines, not a giant system prompt
· “restate it in your own words”
· “use /how first ... then /why”
· “repro this with /verify-<app>“
· “show me a video as proof”
· “/interrogate ... but skeptically”
· “keep a decision log i can audit”
· /correct when it repeats a mistake
the rule: no code until the agent restates the bug and reproduces it
full prompt for Grok Bot + Opus 5.5 in the comments ↓
SpaceXAI engineer Lauren Tan fixes bugs with seven short lines, not a giant system prompt
· “restate it in your own words”
· “use /how first ... then /why”
· “repro this with /verify-<app>“
· “show me a video as proof”
· “/interrogate ... but skeptically”
· “keep a decision log i can audit”
· /correct when it repeats a mistake
the rule: no code until the agent restates the bug and reproduces it
full prompt for Grok Bot + Opus 5.5 in the comments ↓
Full prompt. Paste it into your Grok Bot (model: Opus 5.5):
Take one bug from report to merge, the way Lauren Tan works with her agents. Opus 5.5 does the thinking and the fix. I approve the merge.
SETUP
1. Install pstack (MIT). /how, /why, /verify-<app>, /interrogate and /correct come from it.
2. One bug per thread. I paste the report as-is.
3. No code until the bug is restated and reproduced.
STAGES
RESTATE: "restate it in your own words"
UNDERSTAND: "use /how first ... then /why"
REPRO: "repro this with /verify-<app>"
REVIEW: "/interrogate ... but skeptically"
MERGE: "keep a decision log i can audit"
BRANCH
Repros on main: fix it. Already gone: close early and show the run that proves it.
PROOF
"show me a video as proof". Every fix ships with a recording of the bug before and the fix after. "Done" without proof is not done.
REVIEW
A fresh agent reviews the diff, not the one that wrote it. It looks for what the fix breaks, not what it fixes.
REPEATS
Same mistake twice? Run /correct and turn it into a rule so it never comes back.
REPORT
One message: what broke, why, the proof link, the decision log, and what was not verified.
RULES
Ask before merging, deleting data or touching prod. Two failed tries on a step: stop and tell me why.
Alex retweeted
no way this actually works..
i gave my GrokBots a whole city and now my content runs like a small town at night:
every bot has its own building, its own job and its own little walk to work. when one finishes, it carries the task down the street to the next one
here's who lives there:
• Scout works the Newsroom and flags the AI story before the timeline catches it
• Hook drafts 3 openers in the Prompt Lab, I tap the one that hits
• Reel renders the video in the Studio and patches its own broken renders
• Post queues the thread + video for X and waits for my ok
• Reply clears comments and sorts sponsor DMs
• Ledger heads to the Bank and logs what each post brought in
• approvals, mission board and a live city.log, all on one screen
no tabs. no chasing bots. just a city doing the work, watch it below ↓
the Grok Bot marketplace + 6 bots I'd start with are in the comments. save this
no way this actually works..
i gave my GrokBots a whole city and now my content runs like a small town at night:
every bot has its own building, its own job and its own little walk to work. when one finishes, it carries the task down the street to the next one
here's who lives there:
• Scout works the Newsroom and flags the AI story before the timeline catches it
• Hook drafts 3 openers in the Prompt Lab, I tap the one that hits
• Reel renders the video in the Studio and patches its own broken renders
• Post queues the thread + video for X and waits for my ok
• Reply clears comments and sorts sponsor DMs
• Ledger heads to the Bank and logs what each post brought in
• approvals, mission board and a live city.log, all on one screen
no tabs. no chasing bots. just a city doing the work, watch it below ↓
the Grok Bot marketplace + 6 bots I'd start with are in the comments. save this
Alex retweeted
SpaceXAI engineer Lauren has a simple loop for taking one bug from report to merge
a few short lines, used at the right moments:
· “restate it in your own words”
· “use /how first ... then /why”
· “repro this with /verify-<app>”
· “show me a video as proof”
· “/interrogate ... but
skeptically”
· “keep a decision log i can audit”
same mistake twice? /correct
the trick: no code until the agent has restated the bug and reproduced it
i turned it into one prompt for Grok Bot + Opus 5.5 ↓
save this for your next bug
SpaceXAI engineer Lauren has a simple loop for taking one bug from report to merge
a few short lines, used at the right moments:
· “restate it in your own words”
· “use /how first ... then /why”
· “repro this with /verify-<app>”
· “show me a video as proof”
· “/interrogate ... but
skeptically”
· “keep a decision log i can audit”
same mistake twice? /correct
the trick: no code until the agent has restated the bug and reproduced it
i turned it into one prompt for Grok Bot + Opus 5.5 ↓
save this for your next bug
SETUP
1. Install pstack (MIT). /how, /why, /verify-<app>, /interrogate and /correct come from it.
2. One bug per thread. I paste the report as-is.
3. No code until the bug is restated and reproduced.
STAGES
RESTATE: «restate it in your own words»
UNDERSTAND: «use /how first ... then /why»
REPRO: «repro this with /verify-<app>»
REVIEW: «/interrogate ... but skeptically»
MERGE: «keep a decision log i can audit»
BRANCH
Repros on main: fix it. Already gone: close early and show the run that proves it.
PROOF
«show me a video as proof». Every fix ships with a recording of the bug before and the fix after. «Done» without proof is not done.
STATUSES
REPORTED → RESTATED → UNDERSTOOD → REPRODUCED → FIXED or CLOSED EARLY → REVIEWED → MERGED. A fix I haven’t seen is never «merged».
REVIEW
A fresh agent reviews the diff, not the one that wrote it. It looks for what the fix breaks, not what it fixes.
REPEATS
Same mistake twice? /correct. Turn it into a rule so it never comes back.
REPORT
One message: what broke, why, the proof link, the decision log, and what was not verified.
RULES
Ask before merging, deleting data or touching prod. Two failed tries on a step: stop and tell me why.
Alex retweeted
no way this actually works..
my GrokBots now live in their own city, and it runs my whole content machine:
• Scout sits in the Newsroom and catches the AI story of the day before it blows up
• Hook writes 3 openers in the Prompt Lab, I pick the one that leads
• Reel cuts the video in the Studio, and if the render breaks, it fixes it on its own
• Post ships the thread + video to X straight from the Post Office
• Reply takes care of comments and sponsor DMs
• Ledger heads to the Bank and tallies what every post made
• all the big calls land in one inbox: approve, edit or decline in a click
you don't run the content anymore. you just watch the city work, city below ↓
save this, then read how to build your own GrokBot city in the article below
no way this actually works..
my GrokBots now live in their own city, and it runs my whole content machine:
• Scout sits in the Newsroom and catches the AI story of the day before it blows up
• Hook writes 3 openers in the Prompt Lab, I pick the one that leads
• Reel cuts the video in the Studio, and if the render breaks, it fixes it on its own
• Post ships the thread + video to X straight from the Post Office
• Reply takes care of comments and sponsor DMs
• Ledger heads to the Bank and tallies what every post made
• all the big calls land in one inbox: approve, edit or decline in a click
you don't run the content anymore. you just watch the city work, city below ↓
save this, then read how to build your own GrokBot city in the article below
Alex retweeted
holy f*ck, this is how the engineering lead of elon musk's grok bot sets up her agents. 7 skills, one command, and your agent stops guessing
pstack by lauren tan:
→ /poteto-mode - routes any task through 23 playbooks, reports done only with evidence
github.com/cursor/plugins/tr…
→ /swarm - splits one job across parallel cloud workers, returns one report
github.com/cursor/plugins/tr…
→ /arena - runs several candidates, scores them on a rubric, grafts the best parts together
github.com/cursor/plugins/tr…
→ /figure-it-out - designs the plan for big migrations, keeps or reverts every step
github.com/cursor/plugins/tr…
→ /show-me-your-work - a TSV receipt for every decision: what, why, evidence, result
github.com/cursor/plugins/tr…
→ /reflect - 3 reviewers read your session and turn lessons into skill edits
github.com/cursor/plugins/tr…
→ /make-bot-ui - a page with buttons that wake your grok bot over a webhook
github.com/cursor/plugins/tr…
reflect waits for your ok before editing anything. arena's judge always comes from a different model family. make-bot-ui never takes your key in chat.
start tonight: /add-plugin pstack, then /setup-pstack, then /poteto-mode on your next task.
save this and read the article below to make money with grok bot ↓
holy f*ck, this is how the engineering lead of elon musk's grok bot sets up her agents. 7 skills, one command, and your agent stops guessing
pstack by lauren tan:
→ /poteto-mode - routes any task through 23 playbooks, reports done only with evidence
github.com/cursor/plugins/tr…
→ /swarm - splits one job across parallel cloud workers, returns one report
github.com/cursor/plugins/tr…
→ /arena - runs several candidates, scores them on a rubric, grafts the best parts together
github.com/cursor/plugins/tr…
→ /figure-it-out - designs the plan for big migrations, keeps or reverts every step
github.com/cursor/plugins/tr…
→ /show-me-your-work - a TSV receipt for every decision: what, why, evidence, result
github.com/cursor/plugins/tr…
→ /reflect - 3 reviewers read your session and turn lessons into skill edits
github.com/cursor/plugins/tr…
→ /make-bot-ui - a page with buttons that wake your grok bot over a webhook
github.com/cursor/plugins/tr…
reflect waits for your ok before editing anything. arena's judge always comes from a different model family. make-bot-ui never takes your key in chat.
start tonight: /add-plugin pstack, then /setup-pstack, then /poteto-mode on your next task.
save this and read the article below to make money with grok bot ↓
Alex retweeted
holy f*ck, the engineer behind elon musk's grok bot runs her agents on 7 skills. open source, one install, your agent works like a senior engineer
the pstack stack by lauren:
→ /poteto-mode - restates your goal, picks 1 of 23 playbooks, won't report done without evidence
github.com/cursor/plugins/tr…
→ /swarm - fans one job out to parallel cloud workers, hands back one report
github.com/cursor/plugins/tr…
→ /arena - several candidates on the same task, scored on a rubric, best parts grafted together
github.com/cursor/plugins/tr…
→ /figure-it-out - designs the plan when no playbook fits, runs every step as an experiment
github.com/cursor/plugins/tr…
→ /show-me-your-work - logs every decision: what, why, evidence, result
github.com/cursor/plugins/tr…
→ /reflect - 3 reviewers read your session, each lesson becomes a skill edit
github.com/cursor/plugins/tr…
→ /make-bot-ui - builds a page whose buttons wake your grok bot over a webhook
github.com/cursor/plugins/tr…
reflect asks before it edits any skill. arena's judge never comes from the same model family. make-bot-ui never takes your key in chat.
start tonight: /add-plugin pstack, run /setup-pstack, then /poteto-mode on your next task.
save this and read the article below to make money with grok bot ↓
holy f*ck, the engineer behind elon musk's grok bot runs her agents on 7 skills. open source, one install, your agent works like a senior engineer
the pstack stack by lauren:
→ /poteto-mode - restates your goal, picks 1 of 23 playbooks, won't report done without evidence
github.com/cursor/plugins/tr…
→ /swarm - fans one job out to parallel cloud workers, hands back one report
github.com/cursor/plugins/tr…
→ /arena - several candidates on the same task, scored on a rubric, best parts grafted together
github.com/cursor/plugins/tr…
→ /figure-it-out - designs the plan when no playbook fits, runs every step as an experiment
github.com/cursor/plugins/tr…
→ /show-me-your-work - logs every decision: what, why, evidence, result
github.com/cursor/plugins/tr…
→ /reflect - 3 reviewers read your session, each lesson becomes a skill edit
github.com/cursor/plugins/tr…
→ /make-bot-ui - builds a page whose buttons wake your grok bot over a webhook
github.com/cursor/plugins/tr…
reflect asks before it edits any skill. arena's judge never comes from the same model family. make-bot-ui never takes your key in chat.
start tonight: /add-plugin pstack, run /setup-pstack, then /poteto-mode on your next task.
save this and read the article below to make money with grok bot ↓
Alex retweeted
holy f*ck, this one office turns Obsidian + Opus 5.5 into a Karpathy-grade second brain that works for you 24/7
• Clip saves every paper, repo and thread into raw/ as markdown
• Compile turns raw/ into a real wiki: summaries, concepts, articles that link to each other
• Lint runs health checks: broken backlinks, gaps, notes that contradict each other
• Index keeps the whole vault navigable, no RAG needed
• Quill writes a paid newsletter issue straight from the wiki
• Deal turns it into money: client research packs and a vault template
• anything that costs money or touches clients lands in your inbox: approve, edit or decline in one click
you don't write the wiki. you just say yes
office below ↓
save this, then read how Claude Opus 5.5 + Obsidian gets to $2,100 a month in the article below
holy f*ck, this one office turns Obsidian + Opus 5.5 into a Karpathy-grade second brain that works for you 24/7
• Clip saves every paper, repo and thread into raw/ as markdown
• Compile turns raw/ into a real wiki: summaries, concepts, articles that link to each other
• Lint runs health checks: broken backlinks, gaps, notes that contradict each other
• Index keeps the whole vault navigable, no RAG needed
• Quill writes a paid newsletter issue straight from the wiki
• Deal turns it into money: client research packs and a vault template
• anything that costs money or touches clients lands in your inbox: approve, edit or decline in one click
you don't write the wiki. you just say yes
office below ↓
save this, then read how Claude Opus 5.5 + Obsidian gets to $2,100 a month in the article below








