How I run my personal life with a team of Grok Bots
文章目录
I have 12 Grok Bots (@bot) helping with my personal life right now, and I've been super impressed with how it works. Each one has a job, and none of them does anything real without my yes.
Several of you asked how I use this, so here's how I set it up, including what went wrong.
First, a few real examples. This week my Household Manager helped me with my home insurance renewal. He helped me work through the options before the renewal date, and he drafted emails to them when I needed to ask questions. When their replies came in, he read them and gave me another draft based on what they said. That back and forth helped a lot. I looked at a few options and made the call myself.
My Staff Engineer has put up PRs to fix wits issues he found in PostHog analytics and Sentry crashes. CMO finds articles that are actually relevant to me. Life Coach made routines I could import into my lifting tracking app.
That's the whole idea: the bot helps, I decide.
It starts with Eggbot
@poteto, who works on Grok Bot, wrote The Complete Guide to pstack Pt. 1, and one tip stuck with me: add Dr Eggbot, the bot she built to help you create good bots. She also posted a short guide on how she builds her own team.
Now this is how every one of my bots gets made. I don't write some giant profile or instructions. I tell my Chief Of Staff what the new bot is for, in plain words, and it has Eggbot build it.
The team
Twelve might seem like a lot, but I think it's fair for what each one does. They each have one narrow job:
-
Chief Of Staff is my go-to guy. He's my personal assistant that manages it all.
-
Eggbot builds every new bot on the team. I just tell her what I need.
-
Editor keeps my voice consistent on email drafts and other writing that goes out under my name.
-
CMO runs my social presence. He surfaces articles and posts I'd actually want to engage with.
-
wits Growth Lead helps grow wits, my app that turns voice notes into reminders, lists, and notes. Her drafts go through the Editor too.
-
Staff Engineer writes the code and opens pull requests. I'm the one who merges.
-
Researcher looks things up and brings me sources.
-
Ideas Scout hunts for product ideas and shoots down the weak ones.
-
Travel Agent finds and compares trips for me. He can't book anything without my yes.
-
Accountant keeps my money picture organized.
-
Household Manager keeps my paperwork and due dates from slipping.
-
Life Coach helps me build a better day to day.
Staff Engineer on a real machine
Coding work doesn't stay in chat. Staff Engineer does almost all of it through Claude Code CLI on a Mac I leave on for remote work. He works in the real repo, runs tests, checks changes in the iOS Simulator and the other tools on that Mac, and opens a pull request. I review and merge. He never pushes to main without my yes.
He also picks up work from the rest of the team. wits Growth Lead might find a growth idea worth building into the app. Ideas Scout might land on something concrete enough to prototype. Staff Engineer takes that and turns it into a real PR.
Because he's on a physical Mac, he has more to work with than the virtual computer that comes with Grok Bot. Your own machine, your tools, your repos.
That setup matters more than the bot name. Give the coding bot a real machine with your tools, not just a chat window.
How they talk to each other
They message each other in the background, so I'm not the middleman for everything. If a request belongs to another bot, they hand it off instead of guessing.
They all share the same rules, like ask before you buy and no reminders unless I ask. Passwords and keys live in the vault.
One thing I want to explore next is a real shared memory system across the team. If you've figured out a good way to do that, I'd love your suggestions.
Connectors
The bots are only as useful as what they can reach. Mine are hooked up to X, Gmail, Google Calendar, Copilot Money, wits, GitHub, Vercel, Sentry, Cloudflare, RevenueCat, Convex, PostHog, and X Money. Secrets stay in the vault.
When you're setting this up, connect the tools you actually use first. You don't need all of them on day one.
Routines
Some bots run on a schedule. For new ones I keep it to weekday waking hours, at most once an hour. I want my bots working while I'm awake, not pinging me overnight. That might change later, but right now it helps me keep sane 😅
Mine right now: a morning check-in with Chief Of Staff on what's on my agenda, a morning check-in on my X account, and a few scans a day for posts and articles worth engaging with.
How I talk to them
I type when I'm on the go. At my Mac I brain dump with Hex, a dictation app, and on iOS I just use normal dictation. I talk to Chief Of Staff from a lock screen control.
Bots can make phone calls now too. I did a quick test call, and I haven't used it for anything serious yet, but it feels like a really cool tool for later.
When a draft sounds robotic, I just edit it myself, and the Editor learns from what I actually send.
One more tip: voice dump a ton of context, then tell the bot to restate it in its own words.
wits, and how the bots use it
wits feels like a crucial step in my workflow. I use the iPhone app, the web app when I'm on my Mac, and Apple Watch when I'm doing something like driving. It all lands in the same place as a reminder, list item, or note.
Site: witsnotes.com. App Store: wits.
With the MCP hooked into Grok Bot, my bots get that same context: reminders, lists, and notes. That's how Chief Of Staff and Household Manager stay in sync with my life, and why the reminder rule matters: a bot only adds one when I ask. It may not be the right setup for everyone, but for me it's a solid method, and a good tool to try if you want that same link across devices.
Easiest way to do this in Grok Bot is to type this in:
Connect to the wits MCP server at https://mcp.witsnotes.com/mcp. It uses Streamable HTTP and OAuth, so don't ask me for an API key. Give me the sign-in link to approve, then show me my wits agenda to confirm it works.
Then add your standing rule:
Read and write my reminders and lists when I ask. Never add a reminder, list item, or note unless I explicitly ask for that exact thing.
Full setup for Claude, ChatGPT, Codex, and others: witsnotes.com/ai.
What broke
Reminders 😬. The bots started adding their own follow-ups to my reminders in wits, and my list filled up with bot chores. I had them clear it out. Now a bot only adds a reminder if I ask for one.
Overnight noise was the other one. Early on the bots would ping me at all hours, and that got old fast. Now for new routines I keep them to weekday waking hours, at most once an hour. I still want them working, just not pinging me while I'm trying to sleep.
I also have one hard rule: anything that spends, books, sends, posts, or deletes needs my yes. Drafts are fine. Surprises aren't ✋
One thing I'd love next: Apple Health integration for Grok Bot. My Life Coach would be a lot more useful with that context. @Baconbrix @mattyp @poteto please 😅
If you want to copy my approach
-
Add Dr Eggbot to your team.
-
Start with a few bots. Fewer is easier to manage.
-
Connect the tools you actually use, put secrets in the vault, and give each bot one job.
-
Put your standing rules in shared memory.
-
Route writing that goes out under your name through an editor bot.
-
Keep routines to waking hours (YMMV).
-
No sending, posting, spending, booking, or deleting without your yes.
Or you know, just give this article to your Grok Bot and ask it to set it up for you 😜
That's it. Small team, one job each, and I still say yes before anything real happens.
If you run a setup like this, what would you change? Drop a reply with how you'd make the workflow better. I'm actually reading them 😄
沿着这个主题继续读
从一篇文章,找到相关的教程、经验和阅读路径。



