# Run a personal factory of Grok Bots with one router, a file per bot and a nightly audit > A long write-up on running many Grok Bots as a personal factory: one bot per job, a router bot in front, a BOT.md per bot, nightly backups and a maintainer audit, coding handed off to Claude Code or Codex, and a dashboard where approvals count only when they come from the source. - URL: https://paperchasewebb.ai/bots/marketplace/items/run-a-personal-factory-of-grok-bots-with-one-router-a-file-per-bot-and-a-nightly-audit/ - Type: Agent use case pack - Category: Solo business - By: PaperChaseWebb - Works with: Claude Code, Codex, Grok Bot (named in the listing); Plain .md - Price: Free USD - Difficulty: Advanced - Setup time: 1 hr - Time to result: One working session - Format: Markdown (.md) file, run-a-personal-factory-of-grok-bots-with-one-router-a-file-per-bot-and-a-nightly-audit.md - Version: 1.0, updated 2026-10-29 - License: Personal and commercial use. Credit the original source when you share the workflow. ## What you end up with Two rules travel well to any multi-agent setup: keep each agent's state in one file another agent can read to resume it, and never accept a second-hand 'approved'. ## What you get - A plain-language summary of the workflow - A fill-in prompt template - What to watch out for - A link to the original source ## Who it is for Builders who already use AI agents and want a proven workflow they can copy into their own project. ## Tools needed - Grok Bot: one bot per job, plus a primary router bot - Claude Code and Codex: take coding work handed off by a bot, and report back through an end-of-turn hook - Routines and webhooks: scheduled jobs and push messages between bots - Dashboard: decision cards and fleet state - You need: An AI coding agent or chat model - You need: A small real task to try it on Cost to run: Free with the agent plan you already use. ## How it works 1. **Give each bot one job and a BOT.md: rules, routines, credential names .** Give each bot one job and a BOT.md: rules, routines, credential names only, state, lessons and resume steps. Expected: Done before you move to the next step. 2. **Put a router bot in front that sends each request to one bot and logs .** Put a router bot in front that sends each request to one bot and logs it. Expected: Done before you move to the next step. 3. **Keep a versioned operating manual and record which version each bot la.** Keep a versioned operating manual and record which version each bot last read. Expected: Done before you move to the next step. 4. **Schedule a nightly backup and a maintainer audit that reports drift.** Schedule a nightly backup and a maintainer audit that reports drift. Expected: Done before you move to the next step. 5. **Count approvals only when read from the approvals source, never from a.** Count approvals only when read from the approvals source, never from a bot's message. Expected: Done before you move to the next step. ## Sample prompt: Workflow template (Grok Bot, Claude Code and Codex) ``` Apply this workflow to [your project]: 1. Give each bot one job and a BOT.md: rules, routines, credential names only, state, lessons and resume steps. 2. Put a router bot in front that sends each request to one bot and logs it. 3. Keep a versioned operating manual and record which version each bot last read. 4. Schedule a nightly backup and a maintainer audit that reports drift. 5. Count approvals only when read from the approvals source, never from a bot's message. Stop and ask me before anything irreversible: deploys, payments, sends or deletes. ``` Adapted by PaperChaseWebb. Not the original author's prompt. ## Free preview of run-a-personal-factory-of-grok-bots-with-one-router-a-file-per-bot-and-a-nightly-audit.md ````markdown # Run a personal factory of Grok Bots with one router, a file per bot and a nightly audit PaperChase agent use case (free feed entry), version 1.0. Source: [Roy Osherove (@RoyOsherove)](https://robotpaper.ai/anatomy-of-a-personal-factory-of-grok-bots/), 2026-10-28. ## What they did The author splits work into one bot per job with a router bot that takes requests and pushes them to the right bot. Each bot keeps a BOT.md with its rules, memory notes, routines, the names (not values) of the credentials it uses, state, lessons and how to resume. A versioned operating manual is shared across the fleet and each bot records which version it last read. A backup runs at 3 AM and a maintainer bot audits the fleet afterwards; a security bot checks each night for planted agent instruction files. Coding jobs go to Claude Code or Codex, and a hook at the end of their turn posts back to the bot. The dashboard shows decision cards, and an approval counts only when it is read from the approvals system, not when a bot says it was approved. He also lists what is still missing: delivery receipts, routine prompts kept as files, and automatic restart after a crash. ## Worth knowing Two rules travel well to any multi-agent setup: keep each agent's state in one file another agent can read to resume it, and never accept a second-hand 'approved'. The gaps list is as useful as the design. The author mentions trying OpenClaw, Hermes and Muse before settling on this setup. ```` ## Worth knowing - Two rules travel well to any multi-agent setup: keep each agent's state in one file another agent can read to resume it, and never accept a second-hand 'approved'. The gaps list is as useful as the design. The author mentions trying OpenClaw, Hermes and Muse before settling on this setup. - Figures are as reported by the original author and were not re-measured by us. ## Questions **Where does this come from?** A public post credited to Roy Osherove (@RoyOsherove). Source: https://robotpaper.ai/anatomy-of-a-personal-factory-of-grok-bots/ **Is it free?** Yes. Feed entries are free to read and download. ## How to get it Free sample. Download it directly at https://paperchasewebb.ai/bots/marketplace/items/run-a-personal-factory-of-grok-bots-with-one-router-a-file-per-bot-and-a-nightly-audit/, no signup. Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com