Hermes Agent integration

Entroly is a context engine for Hermes Agent

Entroly implements the Hermes ContextEngine contract so Hermes can select request-only evidence under a model budget, observe completed-turn usage, adapt when the model window changes, report bounded status, and recover the exact pre-compression conversation through a hash-only tool.

Direct answer: Hermes Agent runs the conversation, tools, models, and learning loop. Entroly supplies the context assurance layer: what evidence enters a request, how omitted content can be recovered, and what the integration can report about its context decisions.

Install the Hermes context engine

pip install -U entroly

Install the Entroly context-engine directory into Hermes' context-engine plugin location, then choose Entroly in the Hermes configuration:

context:
  engine: "entroly"

The implementation remains importable without making hermes-agent a required Entroly dependency. When Hermes is installed, Entroly uses the host's ContextEngine interface.

What Entroly adds to Hermes Agent

Request-only selection

select_context() can return a bounded replacement only for the current request. Returning None preserves the original request when it already fits or when safe selection cannot be produced.

Model-aware thresholds

update_model() recalculates the compaction threshold when Hermes switches models or context windows, rather than assuming one fixed budget.

Usage and status

on_turn_complete() observes normalized usage, while get_status() exposes bounded counters and the most recent recovery handle.

Exact replay

When compression changes the request, Entroly stores the canonical pre-compression conversation and exposes one entroly_retrieve(hash) tool for exact full-content recovery.

Hash-only recovery contract

{
  "name": "entroly_retrieve",
  "arguments": {
    "hash": "ccr:0123456789abcdef01234567"
  }
}

The tool accepts exactly one hash argument.
Source paths, natural-language queries, partial hashes, and extra properties are rejected.
The complete stored original is returned; recovery is not another ranking step.
A missing historical handle remains a miss and is not replaced with a newer source revision.

Hermes stays authoritative

Hermes owns the persisted conversation, model provider, authentication, tool loop, memory backend, and agent behavior.
Entroly does not mutate Hermes' persisted history when selecting request context.
System and tool-related messages are protected by the underlying integration's fail-open rules.
The adapter returns the original request when safe bounded context cannot be produced.

Frequently asked questions

Does Entroly replace Hermes' learning loop?

No. Entroly operates at the context boundary. Hermes remains responsible for agent learning, skills, tools, and long-running behavior.

Does the Entroly tool search for related content?

No. entroly_retrieve is deliberately hash-only. Discovery and ranking happen before a recovery handle is known.

What happens if Entroly fails?

The adapter follows a fail-open context policy and preserves the Hermes request rather than breaking the turn.

Can Hermes switch models?

Yes. The integration updates the context length and threshold when Hermes reports a model change.

Inspect the Hermes integration source · Compare all Entroly agent integrations