GrokBot Hedge Fund

Source

Roan (@RohOnChain) — backend / HFT-style execution / prediction-market systems. The viral hook:

x.com/RohOnChain/status/2090490272027418698 (20 Aug 2026) — “build AI hedge fund using GROK BOTS that hunts alpha 24/7.” High bookmark signal (~5.7k bookmarks, ~368k views at capture).

That tweet quotes the long-form article (same day): How to Use Grok Bot to Build an AI Hedge Fund Research Desk · X article . Follow-up 6-page PDF with the production prompts: Drive PDF (21 Aug 2026).

This page is field notes of his architecture. It is not xAI’s official product guide, not a backtest, and not financial advice. He is also offering “first 20 setups” DMs — treat the hype as marketing; steal the desk design if it is useful.

One-sentence TL;DR

Stop prompting ChatGPT one ticker at a time. Name six research bots that share a GrokBot cloud computer and a watchlist file, let five of them generate overnight, and let a sixth Coordinator (checker, not maker) decide what is signal — then you still place the trades.

The actual claim (strip the “hedge fund” headline)

He is not shipping a $2,400 Jane Street. Section X of the PDF is the honest part: this desk is a research layer. It does not replace L2 data, Bloomberg Chat, expert-network calls, broker execution, or historical tick databases.

His cost slide: institutional stack ~$294k/year (Bloomberg $27k + Eikon $22k + sell-side $50k + AlphaSense $15k + junior $180k) vs SuperGrok Heavy $2,400/year (“122×”). That math only holds if you were going to buy the whole stack and if overnight LLM coverage is a substitute for a human junior. It is a coverage argument, not an alpha-proven one.

Prompting vs swarm

Same move as the official GrokBot course and the CEO bot: you stop being the bus between tasks. You design the swarm that routes for you.

• Chatbot forgets between sessions. Swarm writes files on a shared VM.
• Bot A saves. Bot B reads. Bot C appends. Coordinator synthesizes. No glue code.
• You are one floor up: architect of the desk, not the person ctrl-F’ing EDGAR.

Maker-checker is the load-bearing rule. Five upstream bots are makers. The Coordinator never generates raw research — it verifies, ranks, and delivers. He maps that to Citadel / Jane Street / Renaissance: the person who built the signal does not approve the capital. Same idea as front door + specialists.

The six bots

He argues six is the natural sell-side decomposition since the 1970s. Miss one and coverage fails quietly; add more and noise grows faster than signal.

Papers are real. Persistence of those alphas in 2026, on a 100-name retail watchlist, with an LLM reading EDGAR, is not proven here. Treat citations as “why this bot exists,” not as a promised return.

Coordinator rules (the actual edge, if any)

Reply under the tweet that actually lands: “the real advantage will not be access to AI, but knowing which signals to trust.” The Coordinator is that trust layer. If you skip it and read five noisy briefs, you just built a more expensive Bloomberg alert firehose.

Overnight clock (ET)

Sequence is engineered around data freshness, dependency, and parallelism. Independent bots run together; data-sensitive bots run last. Target: whole pipeline under seven hours, brief in inbox by 6 AM ET. Routine window in the PDF: 11 PM ET Sunday–Thursday (US session nights).

Failure handling: retry twice, five-minute backoff; then ping the operator and continue the rest of the sequence so one dead bot does not kill the morning brief. He says production failures cluster on EDGAR rate limits in filing season and missing Seeking Alpha transcripts for small-cap calls.

Shared filesystem (the swarm bus)

Before any bot is created, scaffold the GrokBot computer. This folder tree is the whole coordination trick — same idea as Amrita’s “they talk to each other”, implemented as files:

/workspace/watchlist.csv          ticker, sector, thesis
/workspace/briefs/                dated markdown from each bot
/workspace/cache/filings/         raw SEC PDFs
/workspace/cache/transcripts/     earnings .txt
/workspace/state/                 last-run timestamps + 30-day baselines

Access: SuperGrok Heavy (~$200/mo, bundled) or Cursor Ultra / Teams Premium. Product surface: x.ai/bot. Watchlist cap in the article: up to 100 tickers (Pattern C later talks 3,000 — that is a different deployment, not the $200 desk).

The published prompts

Condensed from his 6-page PDF (21 Aug 2026). Sector Research is described in the article but has no prompt block in the PDF — you still need to write that one from the job description. Stopping conditions he insists on: never “the bot says it ran.” Require checkable facts (“filing exists at EDGAR URL X,” “mention count above 50,” “transcript file >20KB”).

Filings Analyst

You are Filings Analyst. Every night at 11:30 PM ET, read
/workspace/watchlist.csv. For each ticker, check SEC EDGAR for new
filings since the timestamp in /workspace/state/filings_last_run.txt.
For each new 10K, 10Q, 8K, 13F, 13D, or Form 4: download the filing,
save to /workspace/cache/filings/[TICKER]_[FORM]_[DATE].pdf, extract
material changes versus prior same-form filing, flag going-concern
language, auditor change, restatement, insider transactions over $1M,
executive compensation change over 30 percent, or subsequent event
disclosure. Append findings to /workspace/briefs/filings-[YYYYMMDD].md.
Update state timestamp. Deliver by 5 AM ET. Report facts only.

Earnings Analyst

You are Earnings Analyst. Every night at 12:30 AM ET, read
/workspace/watchlist.csv. For each ticker with an earnings call in the
last 24 hours: get full transcript from Seeking Alpha or company IR
page, save to /workspace/cache/transcripts/[TICKER]_[QUARTER].txt,
extract EPS versus consensus, revenue versus consensus, forward
guidance versus prior guidance. Compare CEO and CFO tone versus prior
quarter using Loughran-McDonald negative word list. Flag any material
shift toward: challenging, uncertain, headwinds, cautious, softer,
weaker. Summarize top three analyst Q&A exchanges. Append to
/workspace/briefs/earnings-[YYYYMMDD].md. Deliver by 5 AM ET.

Sentiment Analyst

You are Sentiment Analyst. Every night at 3:30 AM ET, read
/workspace/watchlist.csv. For each ticker: query Grok native X
integration for mentions in last 24 hours, compute mention volume
versus 30-day baseline in /workspace/state/sentiment_baseline.json,
compute sentiment direction from mention corpus, scan Reddit
r/investing and r/stocks for any post over 100 upvotes, scan
StockTwits for volume. Flag any ticker with mention volume 3+ standard
deviations above baseline. Flag sentiment reversals versus 7 days ago.
Append to /workspace/briefs/sentiment-[YYYYMMDD].md. Update baseline
with today's data.

Insider Tracker

You are Insider Tracker. Every night at 1:30 AM ET, read
/workspace/watchlist.csv. For each ticker: check SEC EDGAR for new
Form 4 filings in last 24 hours, check for cluster buying defined as
3+ distinct insiders purchasing within 30-day window, check for
unusual selling defined as single insider selling over $5M or over 25
percent of holdings. Also check new 13F filings from Bridgewater,
Renaissance, Citadel, Two Sigma, Third Point, Tiger Global, D.E. Shaw,
Millennium. For each new 13F extract positions matching watchlist and
flag new initiations, position increases over 25 percent, complete
exits. Append to /workspace/briefs/insider-[YYYYMMDD].md.

Coordinator

You are Coordinator. Every morning at 5:30 AM ET, read all five briefs
from /workspace/briefs/ dated today. Cross-reference findings. Apply
prioritization rules: HIGH CONVICTION requires 2+ bot confirmation on
same ticker; insider cluster buying alone qualifies HIGH standalone;
sentiment alone qualifies only if volume 5+ std devs above baseline;
analyst downgrade alone is MEDIUM at best; multi-source confirmation
is HIGHEST PRIORITY. Deliver unified brief to email at 6 AM ET in
format: HIGH CONVICTION SIGNALS, MEDIUM SIGNALS, SECTOR NOTES, FILINGS
SUMMARY, INSIDER SUMMARY. Save full brief to
/workspace/briefs/coordinator-[YYYYMMDD].md. Push notify any HIGH
CONVICTION signal immediately.

Morning brief + self-improve loop

Brief is the only deliverable. Fixed sections so a human can read it in five minutes and a script can parse it into an analytics stack. He claims he designed the desk once and has not touched the bots since — then immediately describes a week-one noise problem, so believe the loop, not the “set and forget.”

1. Direct prompt iteration. After the brief, message the weakest bot: “you flagged 12 mention spikes, only 2 had news — tighten 3σ to 4σ.” GrokBot updates that bot’s instructions.
2. Retrospective self-correction. “Filings Analyst: review last week. For every flag, did the stock move >2% in the next three sessions? Keep only rules that historically moved price.”

His observed noise curve (five operators, his claim): week 1 ~40% noise → week 2 ~20% after threshold tweaks → week 4 <10% after retrospective rules. First week is supposed to be mediocre. If you expect Jane Street copy on night one, you will kill the desk.

Three deployment patterns

Caveats (read these before you “build a hedge fund”)

• Research ≠ execution. Do not give these bots order-entry keys. Maker-checker only works if the checker cannot also send the order. Same lesson as gymhack: goal-seeking agent + live API = blast radius.
• Overnight drift is real. A reply under the article: unsupervised runs compound silent errors; by morning you are doing damage control, not reviewing progress. His retries help; they do not replace you reading the brief.
• Stopping conditions must be outside the model. File exists. Count exceeded. Byte size. Never “I completed my research.”
• Shared plugins = shared secrets. One GrokBot computer, EDGAR + Gmail + X. Least privilege. See /grokbot guardrails.
• The 122× slide is coverage math. Institutions still win on capital, data feeds, and prime brokerage. He says that too.
• Not investment advice. Cluster-buy alpha is a 2012 journal result. LLMs hallucinate filings. Confirm on EDGAR.

How this maps here

If you only steal one thing: five makers + one checker + files on a shared computer + a 6 AM brief you actually read. Do not skip the checker. Do not auto-trade the brief.

Related on this site

• GrokBot — platform + 100 use cases
• GrokBot course — official Amrita workshop (how bots actually live)
• GrokBot CEO — Coordinator pattern as an org design
• Product brain · Company brain
• God agent vs team · Gym hack

Primary source: @RohOnChain — Grok Bots hedge fund hook · full article · prompts PDF