jev-kit pairs Claude Code with Jev as a judgment layer for browser agents
jev-kit teams Claude Code with TypeSafe's Jev so tool calls pass a rules table first and only ambiguous ones reach Jev, hitting 9/9 browser goals at $0.0008 of Claude cost per run.
I read the jev-kit browser table three times. I was sure the decimal point was in the wrong place someone wired Claude Code and TypeSafe's Jev into one team, and the agent stopped paying a frontier model for every yes/no most people run agents in one of two ways: -> let one big model decide every click, every tool call and every sub-agent, and pay frontier prices for forks a cheap judge could name -> hardcode if/else rules that break the first time the task changes jev-kit splits the stack in two: > the writer: Claude writes the code, the drafts and the text in form fields > the judge: Jev returns a typed choice, score or yes/no with a confidence, in about 0.3 s warm > the guard: every tool call hits a rules table first, only the ambiguous ones reach Jev > the tier check: a sub-agent sent 2+ rungs too expensive gets blocked, cheaper type named > the belay: an agent that says "done" with no passing check gets sent back to verify and the numbers, all measured in the repo: > 9/9 browser goals for $0.0008 of Claude per run vs $0.1868 with Sonnet deciding > 98.2% tier-guard accuracy on 57 scored dispatches, zero false blocks > 33.2 ms added per tool call when no rule matches > 100% on the deny-capable rules eval, zero false denies Claude writes. Jev decides. run it in shadow mode for a week, read the log, then let the cheap judge take the calls
This post quotes another post: x.com/hanakoxbt/status/2110067711363457244