Run an 11-agent team for trading prep
A trader runs 11 Grok Bot agents, each with one job and a scope document, with a Red Team agent that must approve a trade first.
What they did
The trader moved a daily swing-trading prep workflow onto Grok Bot and organized it as 11 separate agents with an org-chart structure, a shared memory layer, and an agentic verification step. Each agent had one job plus MAP.md and CONTRACT.md files to define scope, used its own persistent cloud computer with browser, terminal, and file storage, and a Red Team agent had to pass a trade before anything else moved; the human still kept execution because none of the agents could place trades.
How it went
They say the persistent browsing setup fixed most of the scraping breakage from the earlier system and was easier to set up than Claude Agent Teams. The post gives no performance numbers or P&L, and it leaves open problems around pinning models to agents and understanding Cursor integration.
Worth knowing
The main catch is subscription/tooling tradeoffs: they say Grok Bot was much easier to manage than Claude Agent Teams, assuming you have the right subscription tier.
Labels
They say the persistent browsing setup fixed most of the scraping breakage from the earlier system
the human still kept execution because none of the agents could place trades.
A trader runs 11 Grok Bot agents, each with one job and a scope document, with a Red Team agent that must approve a trade first.
The trader moved a daily swing-trading prep workflow onto Grok Bot
The “Material” label failed its quality check and is not used for selection.
Details
- Agents
- Grok Bot, Claude, Codex
- Source
- Source date
- Oct 7, 2026
- Accounts
- 1
- In registry since
- Oct 12, 2026