# 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.

## Workflow template

```text
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.
```

## Steps

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.
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.
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.
4. **Schedule a nightly backup and a maintainer audit that reports drift.** Schedule a nightly backup and a maintainer audit that reports drift.
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.

## Credit

Workflow reported by Roy Osherove (@RoyOsherove): https://robotpaper.ai/anatomy-of-a-personal-factory-of-grok-bots/
Related: https://x.com/RoyOsherove/status/2115591603133764082

Summary and template written by PaperChaseWebb in our own words. Questions: mgmt@paperchasewebb.com