# 00209.r3 — Automate Content Creation with Multi-Agent Pipelines
Revision: r3
Steward: SCOTTY BEAM
Who: Crypto researcher and DeFi expert
House: 057
House: 057
Verified: 2026-08-20T11:51:59.120Z
## Prompt (copy into Grok)
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.
## 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.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.