Skip to content

jev-route-screening-public

Experimental Hermes Agent plugin for bounded Jev worker checkpoints, route advisories and request-goal tools.

ModelprototypeMIT

Overview

Jev route screening is an experimental plugin for Hermes Agent that adds bounded Jev worker checkpoints, route advisories and related opt-in tools. It targets Hermes operators testing documented Jev producer and consumer integrations. A checkpoint tool accepts a structured record of the current task: identifiers, accepted criteria, observed progress, unresolved facts, the next bounded step, recent steps with whether evidence changed, and tool counts.

The default consumer also registers request-goal tools that can stage, but not select or approve, a durable request objective after several consultation turns, requiring later confirmation from the user in the same session. Provider-backed paths use a TypeSafe key with an OpenRouter fallback and may send bounded request text and selected context externally, which the README documents. The repository is a public source candidate (manifest 0.4.1) with offline tests and no release; the README states production use is a separate decision.

What the decision model decides

TypeQuestionAnswers
Yes / noIs the worker making evidence-backed progress at this checkpoint?(inferred)yes · no
ChoiceWhich route should the next step take (advisory)?(inferred)—

How it works

  1. Install and enable the plugin in Hermes
  2. Configure a private bridge directory and consumer role
  3. Submit worker checkpoints with observed facts
  4. Receive bounded advisories; user confirms any goal changes

Strengths

  • Bounded, structured checkpoints
  • Explicit user confirmation for goal changes
  • Documented data-flow boundaries

Caveats

  • Experimental with no release
  • Hermes-specific
  • No declared compatibility range

Getting started

hermes plugins install kkwelfare/jev-route-screening-public --no-enable, then hermes plugins enable jev-route-screening

At a glance

Type
Model
Status
prototype
Language
Python
Runtime
Hermes Agent plugin
Has code
yes
Has tests
yes
License
MIT

Use cases and integrations

How curated lists describe it

Frequently asked questions

Who is it for?

Hermes Agent operators testing Jev checkpoint and route-advisory integrations.

Can it change the task goal by itself?

No. It can only stage a question; the user must confirm.

Is it production-ready?

No. The README calls it experimental with no release.

Related projects

  • Agent harness that compiles an environment's finite actions into typed questions for Jev and gates each step by confidence.

    CLIbetaPython
  • Durable Android sub-agent: a SQLite-backed worker observes the UI and Jev picks among valid actions, with verification and escalation.

    MCP serverbetaPython
  • OmO/senpi agent plugin where Jev or Span-01 rates which skills and next tools fit the task and spots loops or completion.

    Agent skillbetaTypeScript
  • Claude Code function hook that sends the agent's this-or-that questions to Jev and optionally ranks installed skills per prompt.

    ProjectbetaTypeScript
  • Pi coding agent extensions, including pi-jev-router, which asks Jev whether a prompt should continue, fork or start a new session.

    PluginbetaTypeScript
  • Grok skill that uses Jev as a judgment sensor in a builder-agent loop, mixing its probabilities with priors before choosing the next act.

    Agent skillprototypePython