Another insane Jev use case!
Jev is making it dramatically cheaper to evaluate what actually happened inside an agent run.
And finally, someone open-sourced a self-improving memory layer that can put that signal to work across agent harnesses:
- Claude Code
- Codex
- Cursor
- OpenCode, and 20+ more
Beacon by
@asymptotelabs continuously captures your agent history across harnesses and uses Jev to identify which runs are actually worth learning from.
It then turns the highest-signal workflows, corrections, and debugging patterns into reusable skills.
GitHub repo:
github.com/Asymptote-Labs/ag…
(don’t forget to star it ⭐ )
Beacon preserves the complete session history. But preserving a run and learning from it are two different things.
Most coding-agent sessions contain routine exploration, failed commands, and fixes that only apply to one task. The trace can remain available for inspection without turning every detail into guidance for future agents.
Jev scores each run for evidence, reuse potential, and human correction signals. An application policy then decides whether to promote, review, or discard it.
The recording shows this in action.
Claude receives a coding task, modifies the implementation, and runs the tests. I then provide an edge-case correction, so Claude updates the code and adds regression coverage.
Beacon automatically captures the complete session. Jev evaluates whether the correction contains a reusable engineering lesson.
Once approved, that lesson becomes available to other coding agents working on the project.
Since it works across harnesses:
- Claude Code sessions can teach Codex.
- Cursor debugging can improve OpenCode.
So a problem solved by one agent should not need to be learned from scratch by another.
If you want to dive deeper into Jev, I also wrote a hands-on guide to building this Jev-style decision path with open models, entirely locally.
Read it below.