Video yükleniyor...
Video Yüklenemedi
Jev is quietly taking over the agent stack. If you already have a Jev API key and don't know what to build first, steal this checklist: 1. jev-opus Runs Claude Code on Opus 5.5 and asks Jev before every call how much effort the next step needs: low, medium... show more
29,260 görüntüleme • 1 ay önce •via X (Twitter)
13 Yorum

@ch3nweiii add a checkpoint to assess if the task even needs doing at all. Sometimes we solve the wrong problem.

This is the cleanest split I’ve seen so far. Claude writes, Jev decides the effort, the stop, and the model. The belay hook alone is worth stealing.

Or Cloudflare

babe quick, new jev-larp just dropped

the split isn't hook vs tool, it's who decides: five of these let Jev make the call, the rest only suggest. start with the suggesters — cheapest way to find out if you trust it.

worthy list to build

先让模型自己判断该花多少力气,挺实用的思路

good article

Another one

effort 路由这层有用,但它插在每次调用前,等于把稳定的系统提示前缀又切一刀。想保住 prompt cache,路由决策本身得走本地小模型,否则省下的推理钱又还给路由延迟。

The jev-belay hook checks the transcript when files changed but nothing passed, so the agent needs evidence before it can call the work done.

stealing the commit one

Does the skill router log why it picked a skill, or just the name?
