Adding Jev decision pauses to the Claude Code loop
The author inserts three decision pauses into Claude Code and tests Jev API plus local winnow:e4b on picking test suites: both hit 12/12 bug fixes versus 3/12 for a filename rule.
Decision models are everywhere now, nearly free, so let's get some use out of them in our coding workflows Normally, every Claude Code loop makes small decisions that nobody checks You give it a task, it plans and edits. Then it runs the tests, fixes failures, and hands you a diff It alone decides when to start and when to retry Those are closed questions, the kind decision models answer So I propose three main useful pauses where a decision model picks: > Before coding: is the task clear? > After tests pass: which extra check? > After a failure: retry or ask? I tested the middle pause on 12 bug fixes. Two decision models picked the expected suite on all 12 While a filename rule got only 3, and every picker still caught the one leftover bug I tested Jev (API) and winnow:e4b (locally on my macbook) and scored four pickers against a suite chosen beforehand: > Two decision models: 12 of 12 > Claude code alone: 9 of 12 > A filename rule: 3 of 12 Part 1 shows the full loop and more details (URLs below ↓↓) part 2: how to test a decision model (not live yet, stay tuned) I also built an interactive guide, a full decision model kit and the full test project is on my GitHub ↓↓