Jevflow
Project / 项目 · In the catalogue / 在目录中查看
What Jev decides here · Jev 在这里做什么决定
choice, noul, score: read in the code by a model, not yet by a person 由模型在代码里读到，尚无人复核
a model read the call site; no person yet 模型读过调用点，尚无人复核 · · Cited file / 引用的文件: plugin/jevflow/judge.py
Summary · 摘要
Claude Code plugin that holds the agent to a phased plan, each phase with a definition of done and a check. At each stop it runs them and asks Jev which phase the work is in, how far it got, and whether it is stuck, off goal or claiming done early; a tested policy says go on, next phase or done.written by a model
Claude Code 插件，让智能体按一份分阶段计划工作，每个阶段都有完成标准和检查。每次智能体想停下时，它运行这些检查并询问 Jev：工作处于哪个阶段、进展到哪一步、是否卡住、偏离目标或过早宣称完成；再由经过测试的策略决定继续、进入下一阶段还是结束。模型撰写机翻
Notes · 备注
plugin/jevflow/jev_client.py sends the request to api.typesafe.ai/v1/systemone. Jev is the default judge; Laya, an OpenRouter model or an OpenAI-compatible server can judge instead, and the judge alone never moves a phase forward. Several agents can share one plan. Row drafted from the discovery queue (issue #14) by an AI assistant that read the README and the cited file on 2026-11-04; a maintainer has not yet read the call site.
请求由 plugin/jevflow/jev_client.py 发往 api.typesafe.ai/v1/systemone。Jev 是默认评判模型，也可改用 Laya、OpenRouter 上的模型或 OpenAI 兼容服务；评判模型本身从不推进阶段。多个智能体可共享一份计划。本条目由 AI 助手根据发现队列（issue #14）起草，于 2026-11-04 阅读了 README 和所引文件；维护者尚未亲自阅读调用点。
Launches · 发布记录
Not launched yet. 还没有发布过。 Launch it / 发布它 ↗ · How a product launches / 怎样发布一个产品
Makers · Maker
Made this? Confirm or correct its entry / 这是你做的？确认或更正条目 ↗
The same form takes the product's one line and a demo link, in its maker's own words. 同一个表单也可以补上产品的一句话和演示链接，用 Maker 自己的话。
Badge for its README · README 徽章
[](https://kydlikebtc.github.io/awesome-jev/products/jevflow-parth1811.html)One line for the product's README, linked to this page. The picture says that it is listed; while it is on the launch board, that it is launching; after a week in the top three, its place. It is rebuilt with the site, so the line never needs changing. 放进产品 README 的一行，链接到本页。图片显示已收录；在发布榜上时显示正在发布；进过某周前三后显示名次。它随网站一起重建，这一行不用再改。
Also under this pattern · 同一模式的其他产品
latitude-llm
Open-source observability for AI agents that flags where agents fail in their traces. A shadow provider asks Jev one noul per flagger dimension, at most 11 per call; the cited file does not show whether those answers change any flag, and the README does not mention Jev.
reticle
Checks an agent's "done" by driving the running app and returning pass, fail or cannot tell. Its benchmark harness asks Jev, in one call on captured evidence, five nouls (did the intended consequence happen, is the capture clean, did the app error), a pass/fail/unknown choice and a severity score.
celesto
Secure and persistent computer for AI agents -- build your own Grokbot, and Muse.
atomic
Coding-agent runtime in which workflows are versioned TypeScript stages with executable checks, review gates and human approvals. Its AI package lists Jev from models.dev as a System One decision model on five providers, apart from the chat models; the README does not say where a workflow calls it.
abide
Hooks into Claude Code, Codex, OpenCode and Pi and, on every edit or turn, asks Jev one yes-or-no question per rule in AGENTS.md or CLAUDE.md, showing only the rule and the diff; a broken rule goes back to the agent to fix. On 93 replayed sessions Jev flagged 39 edits; a reviewer confirmed 10.