Grok Bot to prepare a reviewed trading desk
Imran Chatur assembled TradeOps around eleven Grok Bot agents with separate jobs. The system prepared his trading information overnight, updated a database and dashboard, and sent a Telegram digest. A chief-of-staff agent routed the work rather than leaving every agent to do everything.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Prepare a trading review with narrow agent roles, locked predictions and confirmed digest delivery. Check human approval before unattended work and stage broker orders for my execution only.
Reach people exploring AI agents
See placements →What happened
TradeOps produced a database, dashboard, Telegram preparation digest and staged orders; no verified profit or return is claimed.
Reported by Imran ChaturHow the agent did it
- Assign narrow agent roles and written job contracts.
- Require approval and a fresh review before staging any broker order.
- Confirm digest delivery and keep actual order execution with the human.
Where a person stepped in
Chatur retained broker execution; the source documents unapproved weekly plans and changes to the approval checks.
Imran Chatur assembled TradeOps around eleven Grok Bot agents with separate jobs. The system prepared his trading information overnight, updated a database and dashboard, and sent a Telegram digest. A chief-of-staff agent routed the work rather than leaving every agent to do everything.
The workflow had two important action boundaries. A red-team review supplied a fresh pass or fail before a setup could be armed, and another agent staged a broker order. Only Chatur could execute the order. During market hours, five-minute price checks could wake the review process; predictions were recorded and locked before the action stage so later outcomes could be compared with the original assessment.
The account is useful partly because its controls failed. Six of eleven weekly plans between June and September ran without human approval. A Telegram handoff also silently failed. Chatur changed the unattended flows to check approval first and require a single confirmed message, with audit logs and error handling exposing delivery problems.
He reports about twenty database-schema iterations and uses written job contracts to keep agent roles narrow. No verified profit or investment return is supplied. The concrete result is an operational preparation and review system with documented failures and repairs, while broker execution remains a human action.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: liftoffai.substack.com · Imran Chatur
Frequently asked questions
Could an agent execute the broker order?
The described workflow staged an order but reserved execution for Chatur.
What approval failure occurred?
Six of eleven weekly plans between June and September ran without human approval, prompting earlier approval checks.
Why confirm Telegram delivery?
A silent handoff failure meant generation did not guarantee receipt; the author added confirmed delivery and audit visibility.
More details
About this account
Eleven agents maintained trading preparation data, review gates, locked predictions and broker-order drafts.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: Imran Chatur
Source published 5 Oct 2026
Source checked 14 Oct 2026
Tools and topics
Grok Bot · Telegram · TradeOps database · Broker order drafts
Trading preparation · Approval gates · Delivery audit
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.