One-time, explicit copy of provider credentials from one profile to other
profiles from a desktop page. Owner submission (rule 5): repo and tag v1.0.1
pinned at 1599d21d1bce11d94424f749531dadf8d619f42c.
The pin merged in #115599 (eb1ac9b) carries a security gap found during that
review: the run_command_evaluator capability was never consulted, because
AutonomyPolicy was never constructed anywhere in src/. A project at autonomy
level 0 still executed command-type objective evaluators, since the security
allowlist constrains which executable may run and never whether running is
permitted at all.
4f733a8 wires the policy in and fails closed below level 3.
Verified at the new sha against a clean NousResearch/hermes-agent main
checkout: doctor_plugin ok with no findings, read_declaration resolves both
deps from pyproject. Upstream repo gates all pass.
The entry pinned 1.5.0/3bb0a64. v1.5.2 fixes the visualizer layout on
phone, tablet and foldable (navigation was removed below 640px, the
topbar and filter bar overflowed their frame, touch targets were 25px).
The pin is what the installer resolves, so a stale one ships the old UI.
Local-first LanceDB vector memory provider. Registers the memory provider
`lancedb-suite` (the catalog key `lancedb` belongs to the upstream project
lancedb/hermes-agent-memory, which registers the same provider name — the
mnemosyne precedent), pinned at v1.5.0.
The plugin lives in the repository's `plugin/` subdirectory; the pin is a
40-character commit that is also the v1.5.0 tag.
Checks, run at the pinned sha:
- `hermes plugins validate`: all checks green, `security scan — safe`
(the scanner runs on the `plugin/` subdir the CI clones, not the whole repo)
- declared capabilities match reality: the 8 declared tools are exactly the 8
the provider registers
- no self-updating code under the scanned sources
- `hermes plugins install 3L0935/hermes-lancedb-memory-suite/plugin` verified
end to end into a clean HERMES_HOME
Notable behaviour: automatic memory injection is off by default
(`memory.lancedb-suite.auto_prefetch: true` restores it). The core splices
prefetch output onto the user message as relevant context, and a measured
ambiguous query pulled an unrelated memory through the vector path, so recall
is a tool call rather than a push.
One community entry, category memory: Compartment's native Hermes memory
provider, pinned to the commit that adds its register(ctx) entry point and
declares the engine as a plugin dependency. Capabilities are empty, as the
admission probe records for a memory provider.
No code change: the bump adds a README section recording the first real
routed turns, including one off-target suggestion and one miss. Both gates
re-run green at the new pin.
TypeSafe (Jev) skill routing as a pre_llm_call hook: the request is routed
before the model call and the one skill from the live roster that fits it is
named in a single <skill_relevance> line on the user message. Nothing is
injected when nothing fits, and the system prompt is never touched (it is the
prompt-cache prefix).
Opt-in (enabled: false), stdlib only, no self-updating code. Pinned to
DECRUX9812/typesafe-skill-router@82cfa51, where `hermes plugins validate`
passes including the isolated capability probe. Owner submission.
Re-pins to eb1ac9b, which declares fastapi and httpx2 in
[project].dependencies. pyproject previously had dependencies = [], and
Hermes' installer gives pyproject precedence over plugin.yaml's
python_dependencies, so a catalog install resolved no deps at all and the
dashboard half failed to import.
Verified with upstream hermes_cli.plugin_python_deps.read_declaration at
the new sha: specs=('fastapi>=0.104,<1', 'httpx2>=2.7,<3'), source='pyproject'
(it reported specs=() before). doctor_plugin against main: ok, no findings.
Upstream suite: 453 passed, 6 skipped; uv lock --check clean.
