WHAT NEW IN X11.04 WED

AI collections from X · 22 collections · 67,905 posts

jevVIDEO

GrokBot + Jev trading agent risk flow: 7 steps to a 4-hour cooldown

A 7-step setup connects Jev to GrokBot so Jev decides before each order; in testing, three straight losses triggered a 4-hour cooldown and cut drawdown from -18% to -3.2%.

Ochob
@0chobArchived 2026.09.24Originally posted 2026.09.24
Ochob @0chobOriginally posted 2026.09.24
Open original on X

GrokBot + Jev is the first trading agent setup I'd actually let near my account Most trading bots don't blow up on bad entries. They blow up after 3 losses, when they size up and revenge-trade. Mine did. So I split it: GrokBot does the analysis, Jev makes the calls it shouldn't make alone. setup took me 7 minutes: prompt → GrokBot → Jev decides → GrokBot executes → you confirm the order step 1 → get an API key at @typesafeai (never paste it in chat) step 2 → tell GrokBot: save it as TYPESAFE_API_KEY in the secure field step 3 → have GrokBot install typesafe-sdk on Agent Computer + smoke test system_one step 4 → write your risk rules into config: max 1% per trade, 3x leverage cap, 3-loss cooldown step 5 → add the jev-usage-router skill: before any order / resize / re-entry → ask the router, follow its action step 6 → run in shadow mode on paper first, read the logs - kill switch: enabled: false step 7 → go live: Jev decides, GrokBot executes, you confirm every order the result: 3 runs in the video - 3 losses in a row → cooldown 4h, drawdown -3.2% vs -18% without it - 0.6 BTC at 5x → resized to 0.059 BTC, risk capped at 1% - 8 tickers scanned → top 3 ranked, 0 orders sent the sizing rule doing the heavy lifting: size = (equity × risk%) / stop distance The LLM should read the market. It shouldn't be the one deciding when to stop.

This post quotes another post: x.com/ruujss/status/2102774731606991003

x.com/0chob/status/2102810083004395593Archived 2026.09.24 10:14