Using Jev as an agent dispatcher on top of five infrastructure projects
The author suggests adding a Jev dispatcher layer over capabilities like screenpipe, Graphiti, Strix and Cua, using Choice outputs with options, probabilities and confidence to decide the next step.
you gave your AI agent eyes, memory, a security team and a whole computer. who’s deciding what it does next? That’s the question I’d ask before adding another agent. Five projects from the agent map show how much of the infrastructure already exists: → screenpipe: searchable screen and audio history, with capture stored locally by default. https://github.com/screenpipe/screenpipe → Graphiti: facts and relationships with temporal history and links back to their source episodes. https://github.com/getzep/graphiti → Strix: AI-assisted security testing for apps and targets you’re authorized to assess. https://github.com/usestrix/strix → MiroFish: multi-agent simulations built from seed material, for exploring alternative scenarios. https://github.com/666ghj/MiroFish → Cua: computers, desktop automation and sandbox infrastructure for agents. https://github.com/trycua/cua The JEV layer I’d put around those capabilities is a dispatcher. Give it the current goal, the available handlers, the relevant state and what the last action actually returned. Ask a narrow question: which step should happen next? A Choice answer supplies an option, probabilities and confidence. Your code decides how to route it. Need missing context? Retrieve it. Need relationships between facts? Query memory. Need a scenario explored? Run the simulation. Need to operate an interface? Dispatch to the desktop tool. A planning model still owns the broader task; JEV handles bounded judgments inside the loop. The part that matters is what comes back. A click is not proof the task succeeded. A simulation is not proof the forecast is right. Feed the observed result into the next decision, keep the current revision visible, and route ambiguous cases to review. Confidence is not the probability that an answer is correct. These are separate projects, with different setup and licensing requirements. The attached video is an original HTML concept of the proposed routing layer; it doesn’t run the repositories or make live JEV calls. Connecting them requires adapters, permissions and testing. That’s the angle for my JEV article: the planning model sets the direction, JEV supplies narrow judgments, code dispatches allowed actions, and a human reviews consequential changes. Before adding another agent, make its next step inspectable.
This post quotes another post: x.com/0xkurt/status/2103410921892618651