Post
CommunityJev Practices & Patterns
A working note on Jev harnesses for coding agents
A pointer to Diogo Almeida's independent working note on building a Jev harness for coding agents, including why harnesses already make these calls badly.
- Format
- Post
- Reading time
- 3 min
- Published by
- Community
- Author
- st1ne
- Last verified
- Sep 2026
Used inJev for Software & DevTools
Highlights
- Frames harnesses as already making these calls, just with regex parsing.
- Notes the note is independent and not affiliated with the Jev team.
- Structured in sections, starting with the split between harness and model.
Watch out
A pointer post; read the linked note for the actual design.
Questions about this entry
Short answers drawn from the linked project or page.
No. The post summarizes a linked working note by Diogo Almeida, titled a 10-step guide to giving your agent a real decision layer. It gives the three sections and the five calls to move, but the design itself lives in the note, which is where you should read the details.
Files, model, safety, done, and context. The argument is that agent harnesses already make these calls and currently make them badly, by regex-parsing prose replies. Each one becomes a typed Score, Choice, or Noul instead of free text, so the change sits at the decision boundary rather than requiring a rewrite of the loop.
They are the note author's own comparison, not a published rate card. He quotes roughly $605 per 1,000 decisions on cold frontier calls dropping to $0.17 on Jev, about 400x cheaper per decision, with a 0.2s median per call against seconds of LLM latency. Cold versus cached frontier calls does a lot of work in that ratio.
It calls itself an independent working note not affiliated with the Jev team, though the author is Jev's founder and the economics section flatters the product. A reply makes the fairest point: the value is in the failure modes harnesses hit in production, which this post does not expand on.
Jev Engineering: The 10-Step Guide to Giving Your Agent a Real Decision Layer, linked from the poster's card rather than written by him. The X post is a pointer to that article, so the design detail lives on the linked note and not in the thread.
The harness-and-model split: the argument is that agent harnesses already make these decisions, just badly, by regex-parsing the prose replies a chat model returns. The proposal keeps the same boundary but replaces prose parsing with typed calls, so the architecture stays and the interface changes.
Coding agents in general. The poster describes it as a working note on building a Jev harness for coding agents and says the goal is to map the loop, then tells readers to go rebuild their own agent loop. It is not tied to one vendor's harness.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: Decision outputs in Grep
Hacker News: jevmem keeps Claude Code project memory by asking Jev which turns are worth saving.
avinashjetwani61 pointsJevmem – automatic project memory for Claude Code, built on JevRead the thread on Hacker NewsX: How the agent stack moved in Jev's first three days
YouTube: Diogo Almeida tells swyx what System One is, why RLHF failed his automation goal, and why AI should eventually disappear.
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.