Hermes And Other Agent Harnesses
The Hermes provider is a thin integration over coretex-memory-agent and uses
the same memory implementation. It has been exercised through the Hermes
0.19.1 lifecycle, including profile isolation, restart behavior, and M3 event,
pressure, and session-end triggers.
Install the runtime and agent wheels first, then install the Hermes provider artifact advertised by the current kit. Configure it with:
- a persistent store directory;
- the application/user/agent scope mapping;
- the desired CoreTex profile;
- the activated canonical release directory; and
- a context budget appropriate for the model.
The provider maps Hermes lifecycle events as follows:
| Hermes lifecycle | CoreTex operation |
|---|---|
| Before an LLM turn | prefetch and context injection |
| User/assistant turn completed | sync_turn |
| Tool call or tool result | sync_turn with the matching origin |
| Session end | flush_session and M3 consolidation boundary |
| State synchronization | Verify and atomically activate the current canonical release |
Use the provider's release-specific installation and configuration file from
/coretex/v5/kit/manifest; provider entry-point names may change independently
of the memory ABI.
Other harnesses should implement the same small lifecycle adapter. LangGraph,
CrewAI, a custom event loop, or a direct model client can share the same CoreTex
runtime. Map identity into a stable Scope, call prefetch before generation,
call sync_turn after raw events occur, call flush_session at a real session
boundary, and keep canonical-state synchronization outside the request's hot
path.