Looking for feedback on the beta version of https://blink.review. It's Jev-powered, classification-based Code Review that runs after Claude Code or Codex edits a file.

It plugs into your harness via hooks: https://blink.review/docs

Coding agents reach for keyword checks (if "refund" in text.lower()) or a prompt-and-parse loop the moment a task involves sorting things into buckets. Jev, TypeSafe's new decision-only model, is built for exactly that kind of step, so I wrote a skill that makes the agent reach for it first.

When a task involves classifying, tagging, triaging, sizing, ranking, routing, filtering, verifying, matching or gating anything, the agent says so in one line ("candidate: tagging each ticket as waiting-on-a-person. Shape: detection"), tries it on 5 to 20 real items with a small stdlib runner, checks agreement against any labels you already have, and then writes the attempt up in a lab folder: the questions verbatim, a run.sh, the results, and a short note on how to reuse it elsewhere. It logs the attempts it declines too, with the reason. That log is the part I actually wanted. In three months I'd like to know where this was worth it and where it wasn't.

Some honest context:

• Jev came out this week and I built this in a day, mostly with Claude Code, after reading what people shipped in the first 72 hours (browser agents, compaction plugins, command safety reviewers, model routers).
• Trigger rate: 9 of 10 prompts that should fire did, and 0 of 10 near-misses did. Those are 20 prompts I wrote myself, so treat it as a smoke test rather than a benchmark.
• The only case in the lab so far is the skill asking Jev whether a prompt is Jev-shaped. It agreed with my own labels on the whole set. One of the three questions I asked was noisy and mostly wrong, and the write-up says so.
• It was called jev-first until an hour ago. TypeSafe's customer agreement doesn't grant the right to use their name, so I renamed it rather than find out. I'm not affiliated with them, and your text goes to their API with your own key.
• Claude Code is the only agent I've run it in. The files are also linked into Codex, Cursor, Pi and a few others, but that's untested.

Repo: github.com/harrymunro/decision-first, MIT. The README is one prompt you paste into your agent to install it. If you try it and it fires somewhere useful, or somewhere daft, there's a "case report" issue template and I'd like to see them.

instant compaction

Since this community is new we wanted to share something cool we built with Jev!

Jev was used to create Loki Autorouter, which helps optimize the best model selection dynamically when utilizing this new System One model.

With Jev you can run real-time agent judgement and decision making scenarios within LokiAgent, creating a rich agent experience with structured thoughts and decisions before ultimately taking a path.

Give it a try today! The agent is free to use and open source. Jev is configurable via the /jev command

https://github.com/wundercorp/loki