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:

model provider, model name, base URL, temperature, and token settings;
workspace and terminal settings;
NeMo Fabric skills as external skill directories for Hermes Agent;
NeMo Fabric MCP servers as Hermes Agent MCP server config;
tools.blocked as disabled toolsets for Hermes Agent, unioned with harness.settings.disabled_toolsets;
optional NeMo Relay telemetry plugin configuration.

hermes_home configures a base directory. The adapter creates a child under runtimes/<runtime_id> so invocations in one NeMo Fabric runtime share Hermes Agent 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_version must match the adapter contract supported by NeMo Fabric core.
adapter_id is the stable id selected by harness.adapter_id.
adapter_kind is python because NeMo Fabric can invoke it through Python.
runner.module names the persistent host module that NeMo Fabric invokes with python -m.
requirements powers fabric doctor; keep required env vars, binaries, or packages current.
config.accepts must match the NeMo Fabric sections this adapter maps into Hermes Agent.
telemetry.providers declares 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.

Metadata

Release files for nemo-fabric-adapters-hermes 0.1.0a20260725

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nemo-fabric-adapters-hermes 0.1.0a20260725
File	Size	Uploaded
nemo_fabric_adapters_hermes-0.1.0a20260725.tar.gz	6.2 kB	Jul 25, 2026	Details

Release files / nemo_fabric_adapters_hermes-0.1.0a20260725.tar.gz

Download URL	nemo_fabric_adapters_hermes-0.1.0a20260725.tar.gz
Size	6.2 kB
Tags	Source
SHA-256 checksum How to use checksums	`ebe83dbd8e2efc29c7c90291eb0cd60459829bba486f59147463d0a34db31b09`
BLAKE2b-256 checksum How to use checksums	`35bf917a01008f311d11d72445f85951424251b645e6a4b7b4464df0b8196210`
Upload date	Jul 25, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/6.2.0 CPython/3.14.6`