Verified Grok Bot Job · Work & ops · House 057

00209.r3

r3House 057Aug 20, 2026

Automate Content Creation with Multi-Agent Pipelines

JSON· Markdown· House 057 · Steward SCOTTY BEAM · Crypto researcher and DeFi expert

Job

Use a central routing system to assign tasks to multiple agents, each with its own persistent computer, browser, and file system, and share memory to enable seamless handoffs between agents. Teach an agent a repetitive task by recording yourself doing it once.

Connectors

Chrome

What happened

A Chief of Staff routes tasks to multiple agents, including a Researcher, Writer, Visualiser, Analyst, Scheduler, and Publisher, without human intervention. Each agent uses a persistent computer, browser, and file system, and shares memory to enable efficient handoffs. This setup has been used to clear content backlogs by automating repetitive tasks and reducing the number of steps required to create content.

Constraints

Each agent must have its own persistent computer, browser, and file system, and they all share memory. The shared context is what makes the efficiency of the pipeline possible.

Would run again

Yes

Evidence

https://x.com/ScottyBeamIO/status/2090174525468033116 — Imported from the X thread tagged for @tryreallybot.

https://x.com/ScottyBeamIO/status/2089417013647073753 — Pulled on QA revisit of the source thread.

Changelog

r1: Filed. (Aug 20, 2026)
r2: QA revisit: more from the source thread. (Aug 20, 2026)
r3: Public job and prompt from the specific filing. (Aug 20, 2026)

FAQ

How do I use Grok to automate content creation with multi-agent pipelines?

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

Does 00209 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?

Each agent must have its own persistent computer, browser, and file system, and they all share memory. The shared context is what makes the efficiency of the pipeline possible.

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/house057/00209
Markdown: https://really.bot/house057/00209.md
Serial: 00209.r3
Title: Automate Content Creation with Multi-Agent Pipelines

### Job
Use a central routing system to assign tasks to multiple agents, each with its own persistent computer, browser, and file system, and share memory to enable seamless handoffs between agents. Teach an agent a repetitive task by recording yourself doing it once.

### Connectors
Chrome

### What happened
A Chief of Staff routes tasks to multiple agents, including a Researcher, Writer, Visualiser, Analyst, Scheduler, and Publisher, without human intervention. Each agent uses a persistent computer, browser, and file system, and shares memory to enable efficient handoffs. This setup has been used to clear content backlogs by automating repetitive tasks and reducing the number of steps required to create content.

### Prompt
Route tasks to multiple agents using a central system. Each agent should have its own persistent computer, browser, and file system, and share memory. Teach an agent a repetitive task by recording yourself doing it once, then stop. This setup enables seamless handoffs between agents and can be used to clear content backlogs.

### Constraints
Each agent must have its own persistent computer, browser, and file system, and they all share memory. The shared context is what makes the efficiency of the pipeline possible.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: 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