evalroute.yaml 4.4 KB

12345678910111213141516171819
  1. name: evalroute
  2. repo: https://github.com/keppy/hermes-plugin-evalroute
  3. sha: da7593599e62eef52a461507401bca0ca9b5ebf0
  4. description: "Route a task to the right (model, reasoning effort) arm before you start. Classifies the task into a lane, prints a provenance-carrying route card, and installs per-model reasoning-effort defaults. Strong rules run locally; weak-signal classification calls the host LLM and consumes tokens. The separate harness and shim can make paid provider calls when explicitly run; no plugin-owned credentials. Disclosure — weak-signal task classification sends the task text to your active Hermes model via the host LLM facade (token cost). The model-callable tool, /route, /rate and observed /model and /reasoning commands append task text and command args to a local ledger at <HERMES_HOME>/evalroute/labels.jsonl. \"hermes evalroute install-routes\" rewrites agent.reasoning_overrides in config.yaml when you run it. The bundled harness and Hermes shim are never run by the plugin. When run by hand they make paid provider calls, execute model-generated code on the host via shell checkers, and run hermes -z with approvals bypassed. Disclosure — \"hermes evalroute sync\" (run by hand) downloads the route table from the Hugging Face dataset keppy/evalroute-flywheel into HERMES_HOME and route cards then show that dataset's text; \"hermes evalroute dispatch\" (run by hand) spawns a single-query hermes chat on the routed model (Nous provider by default) — or, with --runner claude-code, a `claude -p` (Claude Code) process under the user's own Claude account, whose per-run cost is recorded in the local sidecar — with the brief as its query, inheriting the current environment except HERMES_YOLO_MODE (the worker never inherits --yolo; its approvals follow approvals.single_query_mode, default deny), and writes its report and a .dispatch.json sidecar beside the brief. Disclosure — \"hermes evalroute contribute\" (run by hand only) refuses to run unless evalroute.contribute: true is set in config.yaml, and then uploads redacted outcome rows only — lane, routed arm, confirmed arm, verdict, method, facet counts, ISO week and an HMAC-SHA256 task hash; never task text, notes, paths or the salt — to the user's own path (contributed/<hf-username>/) in the Hugging Face dataset keppy/evalroute-flywheel using the user's existing huggingface_hub login; \"--dry-run\" prints the exact rows and sends nothing; the per-install salt stays local in <HERMES_HOME>/evalroute/contribute.salt. Since evalroute 0.9.1 (schema 2) the same upload also carries lane-correction rows as lane pairs (from_lane, to_lane, method, week) with no task text, plus the max_turns value and harness name the arm ran under and, since evalroute 0.10.0, whether the arm was an explore draw and which default arm it replaced (arm ids only). Disclosure — since evalroute 0.10.0, setting evalroute.explore.fraction in config.yaml (or EVALROUTE_EXPLORE) makes that fraction of routes recommend the lane's runner-up arm from the bundled explore table instead of the default arm (and \"hermes evalroute dispatch\" then runs that runner-up model), marked on the route card; off by default. Disclosure — \"hermes evalroute install-encoder <dir|owner/name>\" (run by hand only) downloads a small text-classification model (the default id keppy/evalroute-lane-encoder is a 146 MB ModernBERT fine-tune on the Hugging Face Hub) into <HERMES_HOME>/evalroute/encoder/ and from then on \"hermes evalroute route\" runs it locally, offline, to classify the task when the keyword rules are weak, instead of the LLM call; it needs torch and transformers in the plugin environment (pip extra evalroute[encoder]), which the plugin does not install; \"install-encoder --remove\" deletes it. \"hermes evalroute export-cases\" (run by hand only) writes your --lane-pinned route rows, task text included, to a local file you name, for training your own encoder; stdout carries counts only and nothing is uploaded. As of 0.6.2 the plugin is a thin adapter: all behaviour lives in the PyPI package evalroute (>=0.10.0,<0.11), declared as a Python dependency that Hermes installs on your confirmation."
  5. maintainer: keppy
  6. tier: community
  7. category: tools
  8. requires_hermes: '>=0.21'
  9. version: "0.6.5"
  10. docs_url: https://github.com/keppy/hermes-plugin-evalroute#readme
  11. capabilities:
  12. provides_tools:
  13. - evalroute_route
  14. provides_hooks:
  15. - pre_llm_call
  16. - pre_command
  17. - post_llm_call
  18. provides_middleware: []
  19. requires_env: []