Hermes And Other Agent Harnesses

Start the installed private sidecar:

./coretex/bin/coretex serve

Wait for "ready": true at http://127.0.0.1:18761. Hermes runs in its own Python 3.11 environment and uses the published coretex-hermes-sidecar connector. Follow the Hermes section of the setup guide. The connector is distributed by the public client repository, separately from the immutable 1.1.0 miner kit.

The guarded coretex-hermes-chat entrypoint waits for confirmed memory writes before returning an answer. Ordinary Hermes CLI/gateway paths remain best effort because Hermes catches provider errors. Recalled records are framed as historical data outside the sealed renderer; a model answer and a durable memory receipt are different observations.

Other harnesses can use AgentMemory or this loopback API: prefetch before generation, sync raw events afterward, flush at the session boundary. The API has no authentication and is private to trusted local processes. Mined Python modules require host trust or external confinement; the serving worker is not the evaluator's kernel sandbox. Stop/restart the sidecar to adopt a new module without replacing executable code during a turn.