A research agent with Opus 5.5 reasoning and a Jev decision layer
The author's research agent reads X posts, GitHub repos, PDF papers and long videos, with Opus handling reasoning and synthesis while Jev controls source selection, investigation depth, model and compute choice, tool failure handling and when to stop.
jev + opus 5.5 is becoming one of my favorite ways to build research agents. i built one that can analyze almost any technical source i give it: → x posts and threads → github repositories → pdf files and papers → lectures and long-form videos Opus: handles the actual reasoning and synthesis. JEV: controls the decisions inside the loop: → which source or tool to use next → how deep the agent needs to investigate → which model + effort level makes sense → what to do when a tool fails → when there is enough evidence to stop researching The result is a research agent that can move across completely different sources without running the most expensive reasoning path for every tiny decision Opus thinks. Jev routes. the harness executes and verifies. This is probably one of my favorite agent architectures i've built so far. i break down how to build the decision layer in the article below:
This post quotes another post: x.com/0xmorlex/status/2101268094387704311