Jev 前置路由,Grok agent 每天省到 0.84 美元
2 万事件先由 Jev 分流为忽略/记录/写作/人工,1.4 万条在生成前被拦下,只有约 800 条唤醒 Grok。

XAI + GROK AGENTS ARE INSANELY CAPABLE UNTIL YOU MAKE GROK DECIDE EVERY TINY THING IN THE LOOP the cleaner setup is to put Jev in front of generation and make every expensive call earn its way in. the shift: routing first, generation second step 1 → collapse messages, repo events, tools and scheduled jobs into one compact event state step 2 → let Jev choose the lane before Grok sees a giant context: ignore / log / write / human step 3 → attach confidence to the route, so uncertainty becomes a real branch instead of another prompt step 4 → kill obvious noise early. in the 20,000-event run, 14,000 events stop before generation step 5 → keep useful state without writing around it. another 4,700 events end as logs step 6 → wake Grok only when language or execution is actually needed. roughly 800 events reach the writing lane step 7 → move risky or unclear cases to human review instead of letting the agent improvise through a guardrail step 8 → keep the route, confidence and handoff visible so the whole desk can be inspected after the run where it gets interesting: Jev handles the decision layer for about $0.84/day in this setup. generation pushes the full loop to roughly $29.04/day. Grok still does the expensive work. Jev just makes sure it only happens when there’s actually expensive work to do. full 5-page breakdown below ↓
这条是引用着另一条写的:x.com/gippp69/status/2103394701063737504