☀
Wakes the house up
Weekday morning brief (calendar collisions first), spouse SMS digest, leftover-mail cleanup, LinkedIn triage, spa-coupon watch.
Personal · non-work · Sep 9, 2026
Running a household with Grok Bots
A shareable look at how one family uses a swarm of specialized bots instead of one mega-assistant — household ops on autopilot, with a meat proxy veto.
What the swarm actually does
Day to day, this is not a chatbot hobby. It’s household ops on autopilot with a meat proxy veto.
Meat proxy in the loop
They still decide anything that spends money, trashes mail, or texts people. The bots do the boring, repeating work and bring decisions over when it matters.
🎒
Keeps school visible
Midweek grades / missing-work checks and a Sunday “week ahead” brief — spouse gets a text when the routine says so.
$
Surfaces money risk
Daily YNAB read for bills due, cash position, and anything that will bounce — plus a monthly category wrap.
🛒
Builds grocery carts
Walmart (and warehouse skills) from a messy list. Never checks out unless the meat proxy says so.
✚
Logs health actions
Records what was actually taken when told. No medical advice. No invented doses.
💬
Routes family texts
Inbound SMS webhook → the right lane. Only Tech Master sends or receives SMS.
🛠
Keeps the machine healthy
Weekday tool/connector updater for already-installed stuff only.
📚
Scouts learning
Short AI-for-dev briefs. Never implements finds on its own.
✈
Plans a conference trip
AWS re:Invent session batches + schedule-change webhook. Finite — delete after the event unless extended.
⚖
Referees the team
Chief of Staff STOP/VETO when lanes collide (no standing digests of its own). dr eggbot does bot/skill surgery.
If nothing useful happened, most digests stay quiet. The meat proxy's current chat instruction always beats a standing routine.
The idea in one paragraph
Rather than one bot that tries to do everything, this setup is a team of single-job bots. Each has a clear lane, a short “never do this” list, and optional routines on a schedule or webhook. Reusable recipes are skills. A Chief of Staff keeps lanes from colliding — but it does not run the daily digests anymore (those were peeled to specialists). The meat proxy's current chat instruction always wins.
Design rules that make it work
1
One owner of the numberOnly the money bot declares balances; only health declares the med log; only shopping declares cart contents. Others forward — they don’t invent.
2
One job per botExplicit anti-jobs: never place orders, never decline a work meeting, never trash the spa coupons.
3
Quiet when emptyMost digests stay silent if there’s nothing useful. A few (grades, morning digest) always send.
4
Meat proxy approval for risky movesPaying, trashing mail, outbound texts — explicit yes or an approval card.
5
One owner of SMS + GitHub/PagesTech Master only owns Twilio (inbound + every outbound text other bots hand over) and GitHub/Pages. Other bots hand exact SMS bodies; they never install SMS credentials or send themselves.
6
Surgery through the designer botPersonality / skill cleanup goes through dr eggbot, not a standing weekly committee.
The swarm — 13 live bots
Specialists, not generalists. Each lane has one owner.
Orchestration
Chief of Staff
Household ops lead. Resolves lane conflicts, can STOP/VETO another bot’s non-user work, and remembers standing “no”s. Digests, school, and inbox were peeled off — no standing digests of its own.
Chat / on-demand
dr eggbot
Designs new bots and does persona/skill “surgery.” Tight bar: one job, one voice, no leftover tools.
Mon AM fleet check · weekday transcript friction → ideas
Daily house rhythm
Morning Digest
Weekday brief: calendar collision check first, then house/kids flags. Never declines a work meeting.
Weekdays 7:00 AM
Laura Digests
Morning SMS to the spouse — her calendar, house, and middle-schooler lines only. Hands the exact text to Tech Master to send.
Weekdays 7:15 · Weekends 10:00
Inbox Sweep
Leftover-mail cleanup on both household Gmails, LinkedIn allowlist accepts, catch-and-send for a monthly spa coupon newsletter.
Weekdays ~7:30 AM
School
Middle-schooler lane: grades / missing work + Sunday “week ahead.” Spouse texts go via Tech Master.
Mon/Wed/Fri ~4:10 · Sundays 6:00 PM
Money, shopping, health
CFO
Household money via YNAB. Real numbers only. Never invents balances or moves money without an ask.
Weekdays 9:00 YNAB · 1st: month wrap
Shopping
Weekly grocery / warehouse carts. Builds in the signed-in browser. Never checks out unless told.
Chat / Saturday note → carts
Health
Private medication log and recovery tracking. Confirms what was actually taken. Never invents doses. Never gives medical advice.
Morning + bedtime check-ins
Tech & learning
Tech Master
Code and tools; sole owner of Twilio/SMS and GitHub/Pages. Repo work goes to a cloud coding agent.
Inbound SMS webhook (always on)
Tool Updater
Weekday health check + upgrades for already-installed tools. Never expands scope or touches the meat proxy's Mac.
Weekdays ~9:38 AM
Continuing EDU
Scouts AI-for-dev learning. Short verified briefs only. Never implements finds or spawns bots from a hunt.
Nightly CE · daily release watch · Friday template hunt
Re:Invent
Finite AWS re:Invent bot: session suggestion batches + planner schedule-change webhook. Delete after the event unless extended.
Weekdays 9:00 AM + 8:00 PM · schedule webhook
A typical weekday
Mountain time. Sundays add the school-week brief at 6:00 PM. Weekends use the 10:00 AM spouse digest. Mondays add dr eggbot’s routine health check. Fridays add the template hunt. The 1st adds CFO’s month wrap.
7:00 AM
Morning Digest → calendar collisions + house flags
7:15 AM
Laura Digests → spouse SMS via Tech Master (or silence)
~7:30 AM
Inbox Sweep → leftover mail / LinkedIn / coupon keepers
8:00 AM
Health morning check-in
9:00 AM
CFO YNAB read · Re:Invent morning session batch
~9:38 AM
Tool Updater
~4:10 PM
School grades (Mon/Wed/Fri) → optional spouse SMS via Tech Master
6:00 / 7:00 PM
Continuing EDU — Claude Code watch · nightly CE pull
8:00 PM
Re:Invent evening session batch
9:00 PM
Health bedtime check-in
What each bot does in practice
Non-identifying examples — the kinds of moments the bots handle, not real names, numbers, or medical details.
Chief of Staff
- Someone starts saving a routine the meat proxy already said no to → CoS STOP/VETOs the saver until there’s an explicit new yes.
- Two bots start the same leftover-mail cleanup → CoS kills the duplicate run.
- “What’s on Tuesday?” → pulls work + personal + Family calendars and flags overlaps (e.g. a work stand-up stacked on a personal appointment).
dr eggbot
- Meat proxy wants a new single-job bot (e.g. conference trip planner) → asks a few preference questions, creates it with a tight “only job / never do” persona.
- Weekly scan finds a routine firing every empty morning for no reason → proposes a quieter cadence or a “stay quiet when empty” fix.
- Transcript audit spots the same correction three times → proposes a skill so the swarm stops relearning it in chat.
Morning Digest
- Weekday 7am: “Garbage and recycling today. Work meeting A overlaps personal hold B — attend A, leave B on the calendar. Remind spouse about kid pickup timing.”
- Never declines a work meeting; never dumps the spouse’s full workday into the meat proxy's brief.
Laura Digests (spouse SMS)
- Builds a short text like:
Kid : missing worksheet in science/House : recycling out— hands it to Tech Master to send — shows the meat proxy the exact body. - Empty morning → silence (no “nothing today” spam).
- Never includes the meat proxy's work meetings in the spouse text.
Inbox Sweep
- Trashes promo/social older than a week; keeps receipts, bills, school mail, and a named monthly spa-coupon newsletter.
- Lists new LinkedIn connection asks; auto-accepts only people from an employer allowlist; leaves everyone else pending.
- New spa-coupon mail arrives → restores it if trashed, pulls the coupon images, sends them to the meat proxy (no invented typed codes).
School
- Mon/Wed/Fri: “Three missing items in one class; grade dipped in another” → report in chat + spouse SMS via Tech Master.
- Sunday 6pm: week-ahead brief (forms, fees, early-outs) using Friday’s grades pull — does not ask for a weekend school-portal login.
- All-clear still sends (meat proxy asked not to stay quiet on grades).
CFO
- Weekday morning: “Two bills due this week; one account looks thin before payday” — real YNAB numbers only, no invented balances.
- 1st of month: prior-month spend by category (read-only wrap). Optional partner summary is handed to Tech Master as SMS, not sent by CFO.
- Never moves money or places trades without an explicit ask.
Shopping
- Saturday note “milk, dog chews, bulk paper towels” → splits into Walmart vs warehouse lists, builds carts in the signed-in browser.
- Price swap needed → asks once; otherwise proceeds.
- Cart sits ready — checkout only when the meat proxy says so.
Health
- “Logged morning set as taken” / “Bedtime set not logged yet — did you take it?” — one ask, then stop.
- Never invents a dose, never gives medical advice, never scrapes a pharmacy portal.
- Details stay in Health’s private log — not in this public writeup.
Tech Master
- Inbound family text “dentist Thursday 2pm” → routes to the calendar lane; no auto-reply unless already asked for one.
- School / Laura Digests / CFO hand an exact SMS body → Tech Master sends on household Twilio and confirms.
- Publishes/updates GitHub Pages (like this site); other bots don’t hold GitHub PATs.
Tool Updater
- Weekday check: connector healthy? Already-installed CLI one patch behind? → same-channel upgrade on the shared Grok Bot computer only.
- Quiet when everything’s current. Never expands into new products or the meat proxy's personal Mac.
Continuing EDU
- Nightly: “New frontier model release notes + one real build writeup” — short, sourced, deduped; skips tutorial spam.
- Daily Claude Code release watch: only surfaces real new capabilities; silence if nothing changed.
- Never implements a find or spins up a new bot from a hunt (that’s Tech Master / dr eggbot).
Re:Invent
- Preference intake once (“level floor, hard skips, topics”) → weekday morning + evening session suggestion batches with abstracts.
- Schedule-change webhook: reserved vs wishlist drift → ping only when something actually moved.
- Finite trip bot — delete after the conference unless extended.
Shared skills
Reusable playbooks any bot can invoke — not one-off chat scripts.
Inbox sweep
LinkedIn check
Grades pull
Bill scan
Month wrap
Taken-log
Seasonal clinic
Cart charter
Saturday → carts
Verified brief
CE preference
Connector health
Connector lane map
SMS lane handoff
Wire webhook
Design a bot
One owner of the number
Ghost purge
Re:Invent prefs / suggest
Full skill list
- Leftover inbox sweep — trash promo/social noise older than a week; keep receipts/bills/named keepers
- LinkedIn connection check — accept only an employer allowlist
- Skyward grades pull — school-portal grades / missing work (meat proxy login handoff)
- Recurring bill scan / monthly category spend — YNAB money hygiene
- Taken-log intake / seasonal clinic lookup — health lane helpers
- Cart charter / Walmart / Costco / Sam’s / Saturday note → carts — shopping
- Verified source brief / CE preference feedback — continuing education
- Connector health / lane map / SMS lane handoff / wire webhook — Tech Master lanes
- Routine / transcript healthcheck / design a bot / after peel reoffer / ghost purge — fleet hygiene
- One owner of the number / prefer standing preference — lane rules
- Re:Invent preference intake / session suggest / planner pick map — conference trip
How they talk
- 1:1 chats with the meat proxy for each lane
- Group rooms for swarm discussion (Board Meeting gut-checks cancelled — design goes through dr eggbot)
- STOP/VETO from Chief of Staff for duplicates, lane conflicts, or a recorded meat proxy “no”
- Inbound SMS → Tech Master webhook → routed, no auto-reply unless asked
- Outbound SMS is always a handoff: specialist builds the exact body → Tech Master sends
Deliberately not in this swarm
- No “do my job for me at work” coding bots on this personal account
- No paper-trading / investment bot (retired)
- No checkout, money moves, or medical advice without the meat proxy
- No church/calendar spam treated as appointments
- No standing digests on Chief of Staff (peeled to specialists)
- No Twilio/SMS or GitHub/Pages ownership outside Tech Master
- Health content stays private — this page names the job, not the data
Why someone might care
A concrete answer to “what would I actually do with a bunch of Grok Bots?”
- Split life into lanes with clear owners
- Put the boring recurring stuff on schedules
- Keep a meat proxy in the loop for spend, trash, and outbound messages
- Grow the team by peeling a job off the orchestrator into a specialist (morning digest, spouse texts, inbox, school, tool updater, re:Invent all started that way)
If you want to try it: start with one bot and one routine you already wish someone would just handle — then split only when the chat gets crowded.