This release is a pre-release and may not be stable for production use.
NVIDIA NeMo Fabric Hermes Agent Adapter
This adapter runs Hermes Agent through its Python SDK.
Install
To install just the Hermes Agent adapter by itself:
pip install "nemo-fabric[hermes]"
To install the Hermes Agent adapter along with the NeMo Fabric Runtime:
pip install "nemo-fabric[hermes, runtime]"
To install the Hermes Agent adapter along with a compatible version of Hermes Agent:
pip install "nemo-fabric[hermes, hermes-agent]"
What It Maps
The adapter receives a normalized payload from NeMo Fabric and materializes a native Hermes Agent configuration for:
- selected model provider, model name, base URL, and temperature through
models; instructions.systemandruntime.max_turns;- workspace and explicit environment variables through
environment; - invocation timeout through
runtime.timeout_seconds; - NeMo Fabric skills as external skill directories for Hermes Agent;
- NeMo Fabric MCP servers as Hermes Agent MCP server config;
tools.enabledandtools.blockedas Hermes-native toolset selection and blocking policy;- optional NeMo Relay telemetry plugin configuration.
Tool selectors are Hermes toolset names because that is the native policy
surface Hermes exposes. Keep Hermes-specific controls such as
terminal timeout, reasoning configuration, and plugin configuration in
harness.settings. The adapter derives Hermes state from the NeMo Fabric
artifact root and creates a child under runtimes/<runtime_id>, so invocations
in one NeMo Fabric runtime share state without sharing config or the session
database with another runtime.
Execution Model
Each NeMo Fabric runtime starts one local adapter host, constructs one Hermes Agent
AIAgent, and opens one SessionDB. Ordered Runtime.invoke(...) calls reuse
those native objects and pass the prior turn's returned transcript back to
run_conversation(...). Runtime stop calls the agent's idempotent close()
method, closes the session database, and releases the Relay plugin context when
enabled.
Hermes Agent Relay telemetry is finalized after each NeMo Fabric invocation so its ATOF
and ATIF artifacts are complete when that invocation returns. This telemetry
boundary does not recreate the AIAgent or SessionDB.
Maintaining The Adapter
Keep fabric-adapter.json aligned with the Python implementation:
contract_versionmust match the adapter contract supported by NeMo Fabric core.adapter_idis the stable id selected byharness.adapter_id.adapter_kindispythonbecause NeMo Fabric can invoke it through Python.runner.modulenames the persistent host module that NeMo Fabric invokes withpython -m.requirementspowersfabric doctor; keep required env vars, binaries, or packages current.config.acceptsmust match the NeMo Fabric sections this adapter maps into Hermes Agent.telemetry.providersdeclares provider-specific outputs and integration modes the adapter can produce or forward.
Do not put end-user agent settings in this directory. Users vary harness,
model, skills, MCP, tools, telemetry, and runtime behavior through complete
typed FabricConfig values and ordinary Python composition. The adapter
descriptor describes adapter capabilities; it is not an agent configuration.
Add descriptor fields only when NeMo Fabric core or the SDK actually uses them.
1 maintainer
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file nemo_fabric_adapters_hermes-0.1.0rc3.tar.gz.
File metadata
- Download URL: nemo_fabric_adapters_hermes-0.1.0rc3.tar.gz
- Upload date:
- Size: 6.4 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
twine/6.2.0 CPython/3.14.6
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
364b203ad8a8a671e379c8fc0b3313490a33bb5bac7bfef57098e4ab14219c08
|
|
| MD5 |
8af163d48f039c68cc6f40f2335e6c41
|
|
| BLAKE2b-256 |
31be101664b4ec37d2fc9c53fae71a8bd3f739c6794d2c6fec78f5c9935b3693
|
