Using Jev as an in-loop judge for unattended Claude Code runs
The author describes a nightly loop where Opus 5.5 writes code and Haiku judges whether the goal is met, comparing it to Jev making millisecond yes/no decisions inside the loop, and shares a setup prompt.
This is f*cking incredible. This Claude Code command fired me from babysitting Opus 5.5 once Opus 5.5 runs your long tasks, stop burning your nights typing "continue", while Haiku sits idle hand the finish line to a judge that isn't Opus and let it run all night run /goal npm test exits 0 and git status is clean, or stop after 20 turns Opus 5.5 writes the code and runs the tests, turn after turn Auto mode approves its tool calls inside each turn Haiku reads the transcript after every turn, never touches a file, and only answers in three ways: → not yet met: Opus takes the reason as its next order and keeps going → met: goal clears and logs an achieved entry → impossible: goal clears with the reason instead of burning tokens till sunrise Opus 5.5 works. Haiku judges. You sleep Jev engineering is the same move one layer down: yes/no calls inside the loop (same error as last turn, did the diff leave scope, retry or stop) go to Jev in ~100 ms, and the big model only thinks where thinking pays anyone still typing "continue" at 2am isn't running an agent, they're its while loop The full tree > Opus 5.5 on high runs the main session > Auto mode approves tool calls inside each turn > /goal holds one measurable end state and a stated check > "or stop after 20 turns" is the leash > Haiku judges after every turn > a prompt-based Stop hook in settings.json does the same for every session paste build and this prompt into Claude Code ↓ "Set up my Claude Code for unattended runs around this tree: 1. Read this repo and my recent sessions and draft three /goal conditions from my real work. > One measurable end state each: a test result, an exit code, an empty queue > A stated check, like "npm test exits 0" > What must not change on the way, plus "or stop after 20 turns" 2. Check ~/.claude/settings.json and .claude/settings.json for disableAllHooks or allowManagedHooksOnly, which switch /goal off 3. Check whether CLAUDE_CODE_GOAL_CHECKIN_MINUTES or ANTHROPIC_DEFAULT_HAIKU_MODEL is set and tell me what each one changes. Report them, change nothing 4. Draft a prompt-based Stop hook for .claude/settings.json that returns ok: false with the reason while my definition of done isn't met, and impossible: true when it can't be met Show me every change as a diff firstly. No moves until I approve" ↳ code.claude. com/docs/en/goal
This post quotes another post: x.com/l1vsun/status/2105630781578125651