00228.r4House 046ResearchAug 31, 202600228

Automate Research with Named Bots

A public log of a finished bot job — verified, serialized, and open to patch.

Read the articleHow to Use Grok Bot to Build an AI Hedge Fund Research DeskJob breakdowns

Prompt (copy into Grok)

1. Collect the list of research verticals and assign each one to a named bot. 2. Look up how to configure bots on a shared cloud computer. 3. Decide on a handoff process for the bots to work together overnight. 4. Return a synthesized brief from the bot swarm by the next morning.

Job

What was asked

1. Collect the list of research verticals and assign each one to a named bot. 2. Look up how to configure bots on a shared cloud computer. 3. Decide on a handoff process for the bots to work together overnight. 4. Return a synthesized brief from the bot swarm by the next morning.

Outcome

What happened

Harish's quants spun up named bots on a shared Google Cloud computer, each bot owning one research vertical, and handed off work to each other overnight, resulting in a synthesized brief landing in Gmail.

Guardrails

Constraints

bots must be named, research verticals must be assigned

Run again

Would they run this again?

Yes

Connectors

Tools this job touched

webGmailGoogle Cloud

Evidence

Proof attached to this serial

https://x.com/im_harish_hari/status/2094259210632479227 — Imported from the X post tagged for @grokbotsh.
https://x.com/RohOnChain/status/2090443377556996209 — Pulled on QA revisit of the source thread.

Changelog

Revisions on this serial

r1Filed.Aug 31, 2026
r2QA revisit: more from the source thread.Aug 31, 2026
r3Public job and prompt from the specific filing.Aug 31, 2026
r4Public job and prompt from the specific filing.Sep 1, 2026

FAQ

Common questions on this job

How do I use Grok to automate research with named bots?+

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

Does 00228 send email without approval?+

This Run used Gmail as a connector. Treat outbound mail as a real action. Constraints on the Run still apply. grokbot.sh does not send mail for you from this page.

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?+

bots must be named, research verticals must be assigned

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

Submit improvement on this Job Prompt

Same job, better version. Copy the prompt, paste it into your AI, paste the reply here. That paste is the only required field. A screenshot or public URL is optional. 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 grokbot.sh.

A patch is the same job, done better. 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 grokbot.sh. The site reads this paste: “What is better” is the only required section. Links and evidence notes in the paste are pulled into the form. Files are optional.

## This Run

URL: https://grokbot.sh/house046/00228
Markdown: https://grokbot.sh/house046/00228.md
Serial: 00228.r4
Title: Automate Research with Named Bots

### Job
1. Collect the list of research verticals and assign each one to a named bot. 2. Look up how to configure bots on a shared cloud computer. 3. Decide on a handoff process for the bots to work together overnight. 4. Return a synthesized brief from the bot swarm by the next morning.

### Connectors
web, Gmail, Google Cloud

### What happened
Harish's quants spun up named bots on a shared Google Cloud computer, each bot owning one research vertical, and handed off work to each other overnight, resulting in a synthesized brief landing in Gmail.

### Prompt
1. Collect the list of research verticals and assign each one to a named bot. 2. Look up how to configure bots on a shared cloud computer. 3. Decide on a handoff process for the bots to work together overnight. 4. Return a synthesized brief from the bot swarm by the next morning.

### Constraints
bots must be named, research verticals must be assigned

Would run again: Yes

### Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph. 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. A public URL of proof if you have one. A note is nice but not required next to the URL.
7. Evidence note? Optional. If you have no URL or file, skip this. The “What is better” paragraph is enough to submit.

## Output format

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

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note

House 046 · Steward Harish · Aug 31, 2026

Automate Research with Named Bots

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Install essential bots from an AI app store for a content week

Research Grok Bot Future Direction

Automate Marketing Tasks

Build a Scalp Trading Bot

Configure a Persistent Cloud Research Environment

Automate Social Media Content Creation and Publishing

Automate Tasks with AI Agents

Implement a Multi-Ledger Architecture

Build a Research Scout for Org Charts

Map a system's signal-to-result flow

Build a Public AI Hedge Fund with HFT Strategies

Automated Content Collection and Processing

Automate Research with Named Bots

What was asked

What happened

Constraints

Would they run this again?

Tools this job touched

Proof attached to this serial

Revisions on this serial

Common questions on this job

Submit improvement on this Job Prompt

Related runs — Same orbit

Install essential bots from an AI app store for a content week

Research Grok Bot Future Direction

Automate Marketing Tasks

Build a Scalp Trading Bot

Configure a Persistent Cloud Research Environment

Automate Social Media Content Creation and Publishing

Automate Tasks with AI Agents

Implement a Multi-Ledger Architecture

Build a Research Scout for Org Charts

Map a system's signal-to-result flow

Build a Public AI Hedge Fund with HFT Strategies

Automated Content Collection and Processing

Command Menu