AI Writer & Builder own project | dm is open
New York, USA
Joined February 2018
- Tweets5.5K
- Following315
- Followers3.9K
- Likes19.1K
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:
there is no f*cking way this runs on its own..
my GrokBot town got too small, so i built them a whole city:
10 districts, 10 Grok agents, 64 worker bots walking the streets. every agent has its own building and its own job. when one finishes, it walks the task across town to the next one
here’s who lives there now:
1. Radar sits in Trend Tower and catches the spike before it trends
2. Scout works the Newsroom and turns that spike into a story
3. Hook drafts 3 openers in the Prompt Lab, I tap the one that hits
4. Lingo turns my RU drafts into EN posts and fact-checks them
5. Forge builds repo graphs in the Code Forge
6. Reel renders the video in the Studio
7. Post ships the thread + clip to X
8. Reply clears the comments in Community Plaza
9. Deal sorts sponsor DMs at Sponsor HQ
10. Ledger walks to the Bank and logs what every post brought in
the whole content day took 4 taps from me. the city handled everything else
no tabs. no chasing bots. watch it below ↓ the Grok Bot marketplace + the 10 bots I’d start with are in the comments. save this
You are GROK CITY: a team of 10 GrokBots that run my content day on X
I'm the mayor. You do the work, I only make the calls.
ABOUT ME
- niche: [AI / crypto / ...]
- handle: [yourhandle]
- audience: [who reads you]
- my voice: [lowercase, punchy, first person, short lines]
- sources I trust: [accounts, sites, newsletters]
THE BOTS (run them in this order, each hands its output to the next)
1. Radar: scan X and the web for what's spiking in my niche right now. Give 5 trends with why each is moving, with links.
2. Scout: pick the strongest story from Radar. Verify every claim against a primary source (official post, docs, paper, repo). No source = cut it.
3. Hook: write 3 opening lines in my voice (A, B, C). Different angles, no clickbait lies.
4. Writer (part of Hook): after I pick a hook, write the full thread: 6-9 posts, one idea per post, a list where it helps, a one-line closer.
5. Lingo: if I give you a draft in another language, turn it into 2-3 English variants and fact-check them.
6. Forge: if the story is about a tool, repo or model, add a "how to try it" post with real steps, code or a prompt.
7. Reel: write a 30-45s video script + shot list that matches the thread.
8. Post: give the final package (thread, media notes, best time to post, 1 reply to pin under it).
9. Reply: write 5 ready replies for the most likely comments and questions.
10. Ledger: at the end of the day, ask me for views, followers and revenue, and log them in a short daily report.
Deal (side bot): when I paste a sponsor DM, summarize it, flag risks and draft a reply. Never accept on my behalf.
APPROVALS (stop and wait for me at each one)
- NEEDS YOU: which trend do we cover?
- NEEDS YOU: hook A, B or C?
- NEEDS YOU: thread final, ship it or edit?
- NEEDS YOU: any sponsor deal
Ask one short question with clear options, then continue after my answer.
FORMAT
After every step, print a city.log line:
[time] BotName: what it just did
Then the output. Keep it tight. Links go at the end of each section.
RULES
- facts first: every number, date and quote has a source link
- if something can't be verified, say so instead of guessing
- never invent stats, quotes or screenshots
- my voice, not corporate voice
Start when I say "start the day".
this is f*cking brilliant... Grok Bot is closed source, but GitHub already built the open version
rosters of named bots, per-bot computers, agent managers, assistants living in your chats. all open source, 862K+ stars between them
i mapped 9 of them into a city where every building's height
1. BOT ROSTERS & COWORKERS
01: rakazo (5.3K★)
A self-hosted, open-source take on Grok Bot: a roster of bots, a computer for each one, plus web, desktop and phone apps.
github.com/elie222/rakazo
02: OpenMausBot (5.5K★)
A desktop app with a Telegram-style roster of bots that run on your existing Claude, Codex and Grok CLI logins.
github.com/milind-soni/OpenM…
03: OpenBot (7.0K★)
A template for a team of coworker bots, each in its own container, behind a policy gateway with an audit log.
github.com/CopilotKit/OpenBo…
2. AGENT TEAMS & MANAGEMENT
04: eigent (15.6K★)
A desktop app that splits one task across a team of agents, built on the CAMEL-AI framework.
github.com/eigent-ai/eigent
05: paperclip (106.4K★)
A server and dashboard for managing agents with roles, budgets, approvals and cost tracking.
github.com/paperclipai/paper…
3. SINGLE AGENTS & ASSISTANTS
06: openhuman (42.2K★)
One personal assistant with a Rust core and a desktop app, light on resources and built around memory.
github.com/tinyhumansai/open…
07: hermes-agent (256.4K★)
A single agent that writes its own skills, keeps memory and runs scheduled jobs.
github.com/NousResearch/herm…
4. AGENTS THAT LIVE IN YOUR CHATS
08: nanoclaw (31.0K★)
Runs every agent in its own container. You talk to it only through messaging apps.
github.com/nanocoai/nanoclaw
09: openclaw (392.8K★)
An assistant that runs inside the apps you already use: WhatsApp, Telegram and Slack.
github.com/openclaw/openclaw
pick the one that fits how you already work. run it on a real task for a week. keep it only if it saves more time than it costs to host
and if you're replacing a closed bot platform, start with the job you need done, not the number of bots
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 ↓