把 Jev 当作 Claude Code / Codex 旁边的决策层

void @sakevoid原推发布于 2026.09.20

在 X 上打开原推

i think people are misunderstanding what jev is. it's not another model that's supposed to replace claude code or codex. it's more interesting as the decision layer sitting next to them. claude/codex are good at the expensive stuff: understanding a repo planning writing code debugging reasoning through weird edge cases but real agents also make hundreds of tiny decisions: should i retry? which tool should run? is this action risky? did the task actually finish? does this require human approval? which model should handle the next step? using a frontier reasoning model for every one of those decisions is overkill. jev is designed for this layer. you give it some state and ask structured questions. it can return a choice, a score, or basically a probability that something is true. so a coding agent could look more like: claude code / codex > understand + execute the task jev > route, classify, score risk, decide retry/escalation deterministic code > enforce permissions and hard rules human > handle high-risk or low-confidence cases example: codex changes authentication code. jev checks: "does this touch a sensitive system?" "how risky is this diff?" "should a human review it?" high confidence + low risk > keep going uncertain > send it back to claude/codex for deeper reasoning high risk > stop and ask a human same thing works for browser agents. you don't need a giant model reasoning for 10 seconds before every click. let the fast model handle the reflexes and wake up the expensive model when actual reasoning is required. that's the part i find interesting. the future agent stack probably isn't one giant model doing everything. it's multiple intelligence layers: fast decisions. slow reasoning. deterministic rules. human escalation. aka less "one ai agent" and more an actual cognitive architecture.