Verified Grok Bot Job · Work & ops · House 309

r2House 30900543.r2Aug 26, 2026

Manage Multiple Bots with a Central Controller

JSON· Markdown· House 309 · scouted on x · Steward Shaishav Pidadi · AI tools that ship

Job

1. Collect information on existing bots and their tasks. Look up the list of tools and services connected to the web. 2. Decide which tasks to assign to the central bot and which to keep separate. 3. Return a report showing the assignment of tasks to the central bot, with a limit of one bot per chore and a maximum of 24 tasks per day.

Connectors

web

What happened

One person set up a central bot to manage other bots, following hourly routines and avoiding extra bots per chore.

Constraints

one chief bot, hourly routines, no extra bot per chore

Would run again

Yes

Evidence

https://x.com/shaivpidadi/status/2092319303429427691 — Imported from a reply on the X thread tagged for @tryreallybot.

Changelog

r1: Filed. (Aug 26, 2026)
r2: Public job and prompt from the specific filing. (Aug 26, 2026)

Also: /takes

FAQ

How do I use Grok to manage multiple bots with a central controller?

Copy the prompt on this serial, connect web, and run it in Grok. Compare the evidence on this page.

Does 00543 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

What constraints were on this job?

one chief bot, hourly routines, no extra bot per chore

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house309/00543
Markdown: https://really.bot/house309/00543.md
Serial: 00543.r2
Title: Manage Multiple Bots with a Central Controller

### Job
1. Collect information on existing bots and their tasks. Look up the list of tools and services connected to the web. 2. Decide which tasks to assign to the central bot and which to keep separate. 3. Return a report showing the assignment of tasks to the central bot, with a limit of one bot per chore and a maximum of 24 tasks per day.

### Connectors
web

### What happened
One person set up a central bot to manage other bots, following hourly routines and avoiding extra bots per chore.

### Prompt
1. Collect information on existing bots and their tasks. Look up the list of tools and services connected to the web. 2. Decide which tasks to assign to the central bot and which to keep separate. 3. Return a report showing the assignment of tasks to the central bot, with a limit of one bot per chore and a maximum of 24 tasks per day.

### Constraints
one chief bot, hourly routines, no extra bot per chore

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note