Using Jev to handle Claude Code's yes/no routing decisions
Routing questions like retry-or-stop and read-the-next-file are handed to Jev for 0.1-second typed decisions, replacing costly Opus 5.5 calls that took $0.40 and 1.4 seconds each.
99% of Claude Code users are running a $20/hour brain on $2/hour tasks and they'll keep doing it because nobody surfaces the routing layer in the docs every session has 5-6 decisions per loop - "which file", "retry or stop", "call this tool", "is this done" those aren't generative questions. they're routing questions Opus 5.5 burning 800 tokens to return "yes, read the next file" isn't intelligence - it's overhead you don't see on the surface three settings that fix it: > effortLevel: high in ~/.claude/settings.json for the main session only > explorer, worker, researcher subagents in .claude/agents/ on medium > Jev handling yes/no forks before an expensive call ever fires Jev turns "retry or stop" into a 0.1s typed decision for almost nothing Opus was spending $0.40 and 1.4 seconds on that same call most people hit "o5.5 is too expensive" and upgrade their plan. the actual fix was never the plan model didn't get dumber. you just stopped asking a surgeon to schedule his own appointments
This post quotes another post: x.com/l1vsun/status/2105630781578125651