NewGrok Bot Jev Router
A small Grok Bot router uses Jev to decide whether to reuse work, stop retries, limit research, or ask for approval.
Added to Jevfast
NewHow it uses Jev
A Python router sends request metadata to the TypeSafe SDK system_one call before Grok Bot performs expensive research, browser, retry, or subagent work. The returned action tells the attached skill whether to reuse an artifact, stop a retry, cap research, or seek human approval.
What Jev decides
Illustrative router classification requestExample answers · not a recorded Jev response · Source ↗
Question 1 · intent
YOUR APP
INSTRUCTION
Classify the main kind of work the request needs.
STATE
The router normalizes goal, work-kind hint, cache presence and note, prior error and repeat count, sources found, and constraints. This summarizes fields sent by code; it does not assert a particular runtime request.
JEV · CHOICE
- chat
- lookup
- research
- browser
- coding
- write
- account
App workflow
- Prepare request state
Pass task metadata and short context to the router; the skill invokes it before tool-heavy work.
- Classify the route
Jev-backed routing returns an action such as reuse_cache, stop_retry, research_capped, or ask_human.
- Observe or honor the action
Shadow mode logs advisory decisions; active mode relies on the Grok Bot skill to honor route.action.
- Run the selected work
Grok Bot carries out research or other actions; sensitive external actions retain a human approval path.
Why it is interesting
It inserts a small typed-decision step before heavier work while keeping execution with Grok Bot. Shadow and active modes, a kill switch, and explicit human-approval boundaries make the routing behavior inspectable.