Jev for code review and coding agents

Niaz Morshed

@niazmorshed_

built `jev-review` @typesafeai it's an experimental, local-first MCP plugin that gives coding agents a score quality feedback loop across different metrics. agents call jev while they work, get scored, make improvements, and repeat the loop try below 👇

Raihan Khan

@raihankhan_rk

I got access to Jev by @typesafeai today morning and I built a cool use case for it Introducing DiffJury - simply paste any public PR link and Jev tells you immediately if it's safe to merge or does it require review ✅ 🔗 Feel free to try it out here - http://diffjury.up.railway.app Imagine Jev being able to tell you if you should merge a PR with grounded context of your codebase. that's what we're building at @graphify 👀 It's fascinating how insanely fast Jev is... the model architecture in itself is quite interesting and this has opened up a plethora of new use cases and I'm sure the internet will pick up on it sooner than anyone'd expect

Oskar

@o_kwasniewski

e2e + jev from @typesafeai ⚡ I'm building an open-source framework for running e2e tests with agents. supports web, mobile (and more!) available soon: tester.army/e2e

Saeed

@stringsaeed

built a highlighter on jev paste any language → my code tokenizes → jev names the lang, colours every word, then says which of 9 lint rules fire and where nine rules in code. jev just answers. near instant lab.saeed.sh/highlight

Jason Lu

@jasonlu_ai

JEV is changes the world of E2E testing! Same eBay test flow, completed-run medians: Jev: 47s / $0.0067 GPT-5.6 Luna: 62s / $0.0277 Claude Sonnet 5: 79s / $0.4062 Try jev-e2e. github.com/perixtar/jev-e…

Wayne Nilsen

@waynenilsen

Jev to unslop Jev as slop linter

云析

@yunxi0623

分享个很火的 skill： typesafe-ai Skill 👇 安装命令：npx skills add typesafe-ai/skills --skill typesafe-ai 可以直接 让 Codex 理解 TypeSafe / Jev 的调用方式 它最有意思的地方，不是让 Jev 替 Codex 写代码，而是把代码里的“判断题”交给 Jev 不过注意它不是装完就会自动接管 Codex 的所有决策，你需要在 Prompt 或代码里明确哪些判断交给 TypeSafe

MajdAICode

@MajdAICode

Following up on my earlier comment: I mapped out the coding-agent workflow I’m exploring in a short video—Cursor, a separate worktree for each feature, and Jev for narrow decisions 👇 x.com/MajdAICode/sta…

MajdAICode

@MajdAICode

One coding-agent pattern I’m exploring: /ticket-triage asks Jev where to look; Cursor checks the repo; Jev flags possible test gaps after the diff. PHPUnit/Playwright verify behavior, and I review before commit. Video: x.com/MajdAICode/sta…

CyrilXBT

@cyrilXBT

JEV IS INSANE your coding agents forget everything the second the session ends. Every fix. Every dead end you already hit. Every "no, not like that." Gone. Tomorrow you teach it all over again. Someone just open sourced the fix, and it runs on Jev. It's called Beacon, by @asymptotelabs. It pulls in your session history from Claude Code, Codex, Cursor, OpenCode and 20+ other agent tools and turns it into one shared memory. But storing everything isn't the hard part. Most agent runs are GARBAGE to learn from. Failed commands. Wrong turns. One off hacks you'd never want repeated. Save all of that and your agent just gets confidently worse. So Beacon keeps the full history, and Jev decides what actually earns a spot in memory. Promote it. Send it for review. Or throw it away. That's a decision you need on thousands of sessions, which is exactly why it has to be cheap. The runs that survive get turned into reusable skills. So something Cursor figured out on Monday shows up in your Claude Code session on Tuesday. Your agents stop starting from zero. Every good run makes the next one smarter. Repo: http://github.com/Asymptote-Labs/agent-beacon Star it and save this. follow @cyrilXBT

Kelbie | Sovran

@KevinKelbie

I made a tool with Jev that reads my whole codebase to answer one question: what should I be looking at? Every chunk of code in your project is scored for relevance.